Specification & Response Document

County of Maricopa 12030-RFP P25 Radio System Infrastructure Upgrade May 17, 2012 including changes made on July 13, 2012 in response to Vendor Questions and additional changes made July 31, 2012 Document 2 - Project Scope, Technical & Functional Specifications and Response Document Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SECTION A - DEFINITIONS USED IN THIS DOCUMENT .................................................................................. 1 SECTION B - OVERVIEW OF EXISTING RADIO SYSTEM .................................................................................. 4 B.1 General.......................................................................................................................................... 4 B.2 Controller ...................................................................................................................................... 4 B.3 Coverage ....................................................................................................................................... 4 B.4 Encryption ..................................................................................................................................... 4 B.5 Dispatch Centers ........................................................................................................................... 4 B.5.1 Sheriff's Dispatch Center ....................................................................................................... 4 B.5.2 Adult Probation Dispatch Center .......................................................................................... 5 B.5.3 Animal Care and Control Dispatch Center ............................................................................ 5 B.5.4 Flood Control District Alert Operations Center .................................................................... 5 B.5.5 Maricopa County Department of Transportation ................................................................. 5 B.5.6 OET Wireless Systems Division ............................................................................................. 5 B.6 Interoperability With Other Regional Radio Networks ................................................................. 5 B.7 Emergency Consoles at Jails.......................................................................................................... 6 B.8 Call Boxes ...................................................................................................................................... 7 B.9 Bi-Directional Amplifiers ............................................................................................................... 7 B.10 Subscriber Radio Inventory ........................................................................................................... 7 B.11 800 MHz Rebanding ...................................................................................................................... 8 B.12 Backhaul ........................................................................................................................................ 8 SECTION C - SCOPE OF WORK ..................................................................................................................... 10 C.1 Project Management .................................................................................................................. 10 C.1.5 Contractor's Project Manager ............................................................................................. 10 C.1.6 Project Plan ......................................................................................................................... 11 C.1.7 Work Locations ................................................................................................................... 13 C.1.8 Contractor's Project Staff .................................................................................................... 14 Section C.1 Response Form..................................................................................................................... 15 C.2 Design and Engineering............................................................................................................... 17 C.2.1 Detailed Design Document ................................................................................................. 17 C.2.2 Requirements for Coverage Maps ...................................................................................... 18 C.2.3 Architecture, Surveying and Civil, Structural, Electrical and Mechanical Engineering ....... 21 Section C.2 Response Form..................................................................................................................... 22 C.3 Licensing and Permitting ............................................................................................................. 24 C.3.1 FCC Licenses ........................................................................................................................ 24 C.3.2 FAA Clearances.................................................................................................................... 24 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade C.3.3 Antenna Structure Registration .......................................................................................... 24 C.3.4 Zoning Variances ................................................................................................................. 24 C.3.5 Construction Permits .......................................................................................................... 24 C.3.6 Environmental Permits ....................................................................................................... 24 Section C.3 Response Form..................................................................................................................... 25 C.4 Site Acquisition Assistance .......................................................................................................... 26 Section C.4 Response Form..................................................................................................................... 27 C.5 Quantities of Equipment to Be Purchased.................................................................................. 28 C.5.1 Dispatch Console Workstations .......................................................................................... 28 C.5.2 Subscriber Radio Equipment ............................................................................................... 28 C.5.3 Jail Emergency Consoles ..................................................................................................... 29 C.5.4 Call Boxes ............................................................................................................................ 29 C.5.5 Key Variable Loaders ........................................................................................................... 29 C.5.6 Alarm and Diagnostic Subsystem User Workstations ......................................................... 29 C.5.7 System Administration Subsystem User Workstations ...................................................... 29 C.5.8 Other Equipment ................................................................................................................ 29 Section C.5 Response Form..................................................................................................................... 30 C.6 Delivery of Materials, Site Construction and Site Improvements, Installation of Equipment .... 31 Section C.6 Response Form..................................................................................................................... 33 C.7 Pre-Installation Testing (Staging or Factory Acceptance Testing) .............................................. 34 Section C.7 Response Form..................................................................................................................... 35 C.8 Programming of Subscriber Radios ............................................................................................. 36 Section C.8 Response Form..................................................................................................................... 37 C.9 Acceptance Testing ..................................................................................................................... 38 Section C.9 Response Form..................................................................................................................... 39 C.10 Archive Documents ..................................................................................................................... 40 Section C.10 Response Form................................................................................................................... 41 C.11 Training ....................................................................................................................................... 42 Section C.11 Response Form................................................................................................................... 43 C.12 Commissioning, Migration and Decommissioning...................................................................... 44 Section C.12 Response Form................................................................................................................... 45 C.13 Final Acceptance ......................................................................................................................... 46 Section C.13 Response Form................................................................................................................... 47 C.14 Warranties .................................................................................................................................. 48 Section C.14 Response Form................................................................................................................... 49 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona C.15 12030-RFP P25 Radio System Infrastructure Upgrade Optional Post-Warranty Maintenance and Repair Services ....................................................... 50 Section C.15 Response Form................................................................................................................... 51 C.16 Time to Complete Project ........................................................................................................... 52 Section C.16 Response Form................................................................................................................... 53 SECTION D - TECHNICAL AND FUNCTIONAL SPECIFICATIONS .................................................................... 54 D.1 Radio System Architecture and General Requirements ......................................................... 54 D.1.1 General Requirements ........................................................................................................ 54 D.1.2 Internet Protocol ................................................................................................................. 54 D.1.3 Windows 7 .......................................................................................................................... 55 Section D.1 Response Form .................................................................................................................... 56 D.2 Workmanship Requirements ...................................................................................................... 57 D.2.1 Quality Program .................................................................................................................. 57 D.2.2 Grounding, Lightning and Transient Suppression ............................................................... 58 D.2.3 Cabling................................................................................................................................. 58 D.2.4 Installation of Equipment.................................................................................................... 59 Section D.2 Response Form .................................................................................................................... 61 D.3 Safety Program............................................................................................................................ 63 D.3.1 Safety Studies, Training and Awareness ............................................................................. 63 D.3.2 Safety Equipment ................................................................................................................ 63 D.3.3 Safety Inspections ............................................................................................................... 63 D.3.4 Safety Reporting and Safety Monitoring ............................................................................ 63 D.3.5 Other Elements ................................................................................................................... 63 Section D.3 Response Form .................................................................................................................... 64 D.4 Selection of Antenna Sites .......................................................................................................... 65 Section D.4 Response Form .................................................................................................................... 67 D.5 Site Acquisition Assistance .......................................................................................................... 68 Section D.5 Response Form .................................................................................................................... 70 D.6 Environmental, Biological, Cultural ............................................................................................. 71 Section D.6 Response Form .................................................................................................................... 72 D.7 Site Preparation .......................................................................................................................... 73 D.7.1 Temporary Access Roads During Project Work .................................................................. 73 D.7.2 Permanent Access Roads for Maintenance Access ............................................................ 73 D.7.3 Helicopter Access Sites ....................................................................................................... 73 D.7.4 Utilities ................................................................................................................................ 73 D.7.5 Grading and Earthwork ....................................................................................................... 74 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona D.7.6 12030-RFP P25 Radio System Infrastructure Upgrade Basic Site Requirements...................................................................................................... 74 Section D.7 Response Form .................................................................................................................... 75 D.8 Optional Low Environmental Impact Antenna Sites ................................................................... 76 D.8.1 Mini-Site .............................................................................................................................. 76 D.8.2 Micro-Site ............................................................................................................................ 76 D.8.3 Other Configurations .......................................................................................................... 77 Section D.8 Response Form .................................................................................................................... 78 D.9 Site Engineering, Plans & Construction Drawings....................................................................... 79 D.9.1 Geotechnical Report ........................................................................................................... 79 D.9.2 Structural Analysis............................................................................................................... 79 D.9.3 Plans and Drawings ............................................................................................................. 79 D.9.4 Ownership of Plans, Drawings, Documents, and Specifications ......................................... 80 Section D.9 Response Form .................................................................................................................... 81 D.10 Site Primary Power Specifications .............................................................................................. 82 D.10.1 Commercial AC Power......................................................................................................... 82 D.10.2 Photovoltaic ("Solar") Power Systems ................................................................................ 82 Section D.10 Response Form .................................................................................................................. 84 D.11.1 Battery Capacity .................................................................................................................. 86 D.11.2 Battery Chemistry ............................................................................................................... 86 D.11.3 Rectifiers/Chargers.............................................................................................................. 86 D.11.4 Low-Voltage Disconnect ..................................................................................................... 87 D.11.5 DC to DC Converters ........................................................................................................... 88 D.11.6 DC to AC Inverters ............................................................................................................... 89 D.11.7 DC Power Distribution......................................................................................................... 90 Section D.11 Response Form .................................................................................................................. 91 D.12 Backup AC Power Generators ..................................................................................................... 95 D.12.1 General ................................................................................................................................ 95 D.12.2 Fuel ...................................................................................................................................... 95 D.12.3 Engine.................................................................................................................................. 95 D.12.4 Outdoor Installation ............................................................................................................ 95 D.12.5 Furnished Complete ............................................................................................................ 96 D.12.6 Ratings ................................................................................................................................. 96 D.12.7 Generator Set Control ......................................................................................................... 97 D.12.8 Cranking Control ................................................................................................................. 97 D.12.9 Generator Protection Controls (per NFPA-110).................................................................. 97 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.10 Generator/Transfer Switch Alarms ................................................................................. 97 D.12.11 Generator Front Panel Metering .................................................................................... 98 D.12.12 Generator Front Panel Controls ...................................................................................... 98 D.12.13 Generator Fuel Tank ....................................................................................................... 98 D.12.14 Transfer Switch ............................................................................................................... 99 D.12.15 Start-Up Service ............................................................................................................ 102 Section D.12 Response Form ................................................................................................................ 103 D.13 Uninterruptible Power Supplies................................................................................................ 108 D.13.1 Modular............................................................................................................................. 108 D.13.2 User-Replaceable, Hot-Swappable Modules .................................................................... 108 D.13.3 Capacity of UPS ................................................................................................................. 108 D.13.4 Runtime ............................................................................................................................. 108 D.13.5 Redundancy....................................................................................................................... 108 D.13.6 Bypass Switch .................................................................................................................... 108 D.13.7 Modes of Operation .......................................................................................................... 108 D.13.8 Ratings ............................................................................................................................... 109 D.13.9 Batteries ............................................................................................................................ 110 D.13.10 Metering and Diagnostics ............................................................................................. 110 D.13.11 Start-Up Service ............................................................................................................ 112 Section D.13 Response Form ................................................................................................................ 113 D.14 Antenna Support Structures ..................................................................................................... 116 D.14.1 New Antenna Support Structures ..................................................................................... 116 D.14.2 Existing Antenna Support Structures ................................................................................ 116 D.14.3 Standards .......................................................................................................................... 116 D.14.4 Materials ........................................................................................................................... 116 D.14.5 Height ................................................................................................................................ 117 D.14.6 Loads, Stresses and Other Design Considerations ............................................................ 117 D.14.7 Cable Ladders .................................................................................................................... 120 D.14.8 Obstruction Lighting and Marking .................................................................................... 121 D.14.9 Ice Shields.......................................................................................................................... 122 D.14.10 Climbing Ladder ............................................................................................................ 122 Section D.14 Response Form ................................................................................................................ 123 D.15 New Prefabricated Equipment Shelters.................................................................................... 126 D.15.1 Structural Requirements ................................................................................................... 126 D.15.2 Roof ................................................................................................................................... 126 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.15.3 Exterior Finish ................................................................................................................... 127 D.15.4 Interior Finish .................................................................................................................... 127 D.15.5 Other Requirements ......................................................................................................... 127 Section D.15 Response Form ................................................................................................................ 129 D.16 Buildings Constructed On-Site .................................................................................................. 131 D.16.1 Structural Requirements ................................................................................................... 131 D.16.2 Roof ................................................................................................................................... 132 D.16.3 Exterior Finish ................................................................................................................... 132 D.16.4 Interior Finish .................................................................................................................... 132 D.16.5 Other Requirements ......................................................................................................... 132 Section D.16 Response Form ................................................................................................................ 133 D.17 Requirements Common to All Equipment Spaces .................................................................... 134 D.17.1 New Equipment Spaces..................................................................................................... 134 D.17.2 Existing Equipment Spaces................................................................................................ 134 D.17.3 Size .................................................................................................................................... 134 D.17.4 Electrical Power................................................................................................................. 134 D.17.5 Floors................................................................................................................................. 135 D.17.6 Interior Lighting................................................................................................................. 135 D.17.7 Exterior Lighting ................................................................................................................ 136 D.17.8 Exterior Doors ................................................................................................................... 136 D.17.9 HVAC ................................................................................................................................. 136 D.17.10 Transmission Line Entry Port ........................................................................................ 137 D.17.11 Interior Cable Ladder .................................................................................................... 138 D.17.12 Fire Protection System .................................................................................................. 138 D.17.13 Grounding and Lightning Suppression .......................................................................... 139 Section D.17 Response Form ................................................................................................................ 140 D.18 Site Physical Security................................................................................................................. 143 D.18.1 Fencing .............................................................................................................................. 143 D.18.2 Access Road Gates ............................................................................................................ 145 D.18.3 Padlocks ............................................................................................................................ 146 D.18.4 Americans with Disabilities Act Compliance ..................................................................... 146 Section D.18 Response Form ................................................................................................................ 147 D.19 Misc. Site Amenities .................................................................................................................. 149 D.19.4 Protection From Falling Ice ............................................................................................... 150 Section D.19 Response Form ................................................................................................................ 151 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona D.20 12030-RFP P25 Radio System Infrastructure Upgrade Trunked/LMR Subsystem RF Coverage Requirements ............................................................. 152 D.20.1 Limiting Case ..................................................................................................................... 152 D.20.2 Definitions ......................................................................................................................... 152 D.20.3 Required Radio Coverage.................................................................................................. 152 D.20.4 Balanced Talk-Out and Talk-Back Coverage .................................................................... 157 D.20.5 Coverage Inside Buildings ................................................................................................. 157 D.20.6 Radio Frequency Noise and Interference at Antenna Sites .............................................. 158 Section D.20 Response Form ................................................................................................................ 159 D.21 Trunked/LMR Subsystem Functional and Technical Requirements ......................................... 162 D.21.1 700 MHz ............................................................................................................................ 162 D.21.2 Project 25 Phase 2 ............................................................................................................. 162 D.21.3 Trunking ............................................................................................................................ 162 D.21.4 Traffic Capacity.................................................................................................................. 162 D.21.5 Wide-Area Operation ........................................................................................................ 163 D.21.6 Trunked Feature Set.......................................................................................................... 163 D.21.7 Master Network Switch .................................................................................................... 168 D.21.8 Network Components ....................................................................................................... 169 D.21.9 Base Stations/Repeater Stations....................................................................................... 169 D.21.10 Receiver Comparators................................................................................................... 170 D.21.11 Radio System Expansion Capabilities ............................................................................ 170 D.21.12 Base Station/Repeater Antennas .................................................................................. 171 D.21.13 Coaxial Cable Specifications .......................................................................................... 171 D.21.14 Transmitter Combiner Specifications............................................................................ 172 D.21.15 Receiver Multicoupler Specifications............................................................................ 173 D.21.16 Tower-Top Amplifier Specifications .............................................................................. 173 D.21.17 Optional Upgrade of Bi-Directional Amplifier Systems................................................. 174 D.21.18 Encryption ..................................................................................................................... 174 D.21.19 System Access and Security .......................................................................................... 175 D.21.20 GPS Location Reporting Capability ................................................................................ 176 D.21.21 Emergency Consoles at Jails .......................................................................................... 177 D.21.22 Interoperability Features .............................................................................................. 178 D.21.23 Call Boxes ...................................................................................................................... 180 D.21.24 Control Stations for Communication with Sites in "Site Trunking" Mode .................... 180 Section D.21 Response Form ................................................................................................................ 182 D.22 Dispatch Console Subsystem Functional & Technical Specifications........................................ 190 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.22.1 Features and Functions ..................................................................................................... 190 D.22.2 Emergency Alarm Functionality ........................................................................................ 193 D.22.3 Console Patch Functionality .............................................................................................. 194 D.22.4 Other Features and Functions .......................................................................................... 195 D.22.5 Logging Recorder .............................................................................................................. 196 D.22.6 Existing Control Stations and Base Stations ...................................................................... 197 Section D.22 Response Form ................................................................................................................ 198 D.23 Backhaul Subsystem Functional & Technical Specifications ..................................................... 202 D.23.1 Capacity ............................................................................................................................. 202 D.23.2 Optional Additional Capacity ............................................................................................ 202 D.23.3 Existing County Fiber Optic Network ................................................................................ 202 D.23.4 Ethernet and Internet Protocol......................................................................................... 202 D.23.5 Multi-Protocol Label Switching ......................................................................................... 203 D.23.6 Redundancy and Reliability ............................................................................................... 203 D.23.7 Microwave Equipment ...................................................................................................... 204 D.23.8 Fiber-Optic Equipment ...................................................................................................... 204 D.23.9 Diagnostics, Controls and Alarms ..................................................................................... 204 D.23.10 Other Requirements ..................................................................................................... 205 Section D.23 Response Form ................................................................................................................ 207 D.24 Alarm and Diagnostic Subsystem Functional & Technical Specifications ................................. 209 D.24.1 Consolidated System ......................................................................................................... 209 D.24.2 Architecture ...................................................................................................................... 209 D.24.3 Alarm and Diagnostic Workstations ................................................................................. 210 D.24.4 Security ............................................................................................................................. 210 Section D.24 Response Form ................................................................................................................ 211 D.25 System Administration Subsystem Functional & Technical Specifications............................... 212 D.25.1 System Usage Reports....................................................................................................... 212 D.25.2 System Configuration Functions ....................................................................................... 212 D.25.3 Subscriber Radio Unit Management ................................................................................. 213 D.25.4 Real-Time System and Talkgroup Usage Data .................................................................. 213 D.25.5 Selective Disablement of Field Units................................................................................. 213 D.25.6 Security ............................................................................................................................. 214 Section D.25 Response Form ................................................................................................................ 215 D.26 Electronic Security Systems ...................................................................................................... 217 D.26.1 May 17, 2012 Video Surveillance ............................................................................................................. 217 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona D.26.2 12030-RFP P25 Radio System Infrastructure Upgrade Site Access Control ............................................................................................................ 217 Section D.26 Response Form ................................................................................................................ 218 D.27 Acceptance Testing Requirements ........................................................................................... 219 D.27.1 Pre-Installation (Factory) Acceptance Testing .................................................................. 219 D.27.2 Component Acceptance Testing ....................................................................................... 219 D.27.3 Sub-System Acceptance Testing ....................................................................................... 220 D.27.4 System Functional Acceptance Testing ............................................................................. 221 D.27.5 Radio Coverage Verification Acceptance Testing ............................................................. 222 D.27.6 Ninety-Day Reliability Acceptance Test ............................................................................ 223 Section D.27 Response Form ................................................................................................................ 224 D.28 Training Specifications .............................................................................................................. 226 D.28.1 End-User Training.............................................................................................................. 226 D.28.2 Dispatcher Training ........................................................................................................... 226 D.28.3 Training for Maintenance Personnel and System Administrators ................................... 227 D.28.4 Executive and Management Familiarization..................................................................... 229 D.28.5 Source Materials ............................................................................................................... 229 D.28.6 Training Locations ............................................................................................................. 229 D.28.7 Early Delivery of Certain Training Classes ......................................................................... 229 D.28.8 Scheduling of Training ....................................................................................................... 229 Section D.28 Response Form ................................................................................................................ 231 D.29 Requirements for Commissioning, Migration and Decommissioning ...................................... 234 D.29.1 Single End-User User Cutover ........................................................................................... 234 D.29.2 No Manual Roaming ......................................................................................................... 234 D.29.3 Cutover Rollback Plan ....................................................................................................... 234 D.29 4 Project Schedule Shall Be Based on Cutover Requirements ............................................. 234 Section D.29 Response Form ................................................................................................................ 235 D.30 Archive Documents ................................................................................................................... 236 D.30.1 Construction Drawings ...................................................................................................... 236 D.30.2 Materials List ..................................................................................................................... 236 D.30.3 Block Diagrams and Schematic Diagrams ......................................................................... 236 D.30.4 Operating and Maintenance Manuals .............................................................................. 236 D.30.5 Acceptance Test Documentation ...................................................................................... 236 D.30.6 Training Materials ............................................................................................................. 236 D.30.7 Software ............................................................................................................................ 236 D.30.8 Document Formats ........................................................................................................... 236 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.30 Response Form ................................................................................................................ 238 D.31 Warranties ................................................................................................................................ 239 Section D.31 Response Form ................................................................................................................ 240 D.32 Requirements for Optional Post-Warranty Maintenance and Repair Services ........................ 241 D.32.1 Software Maintenance and Repair ................................................................................... 241 D.32.2 Depot Repair of Field Replaceable Units ("FRUs") ............................................................ 242 D.32.3 Complete Troubleshooting and Repair of the Radio System ............................................ 243 D.32.4 Remote Monitoring of the Radio System by the Contractor ............................................ 246 D.32.5 Preventive Maintenance Program for Radio System Electronic Systems ......................... 246 D.32.6 Depot Repair of Subscriber Radio Equipment by the Contractor ..................................... 247 D.32.7 Field Service of Mobile Subscribers .................................................................................. 248 D.32.8 Field Service of Control Station Subscribers ..................................................................... 250 D.32.9 Factory Technical and Engineering Support ..................................................................... 251 D.32.10 Purchase of Replacement Parts, Components and Accessories ................................... 252 D.32.11 Physical Plant Maintenance .......................................................................................... 252 Section D.32 Response Form ................................................................................................................ 254 SECTION E - SUBSCRIBER RADIO EQUIPMENT TECHNICAL & FUNCTIONAL SPECIFICATIONS .................. 260 E.1 Multiband Subscribers .............................................................................................................. 260 E.2 General Requirements for All Subscribers ................................................................................ 262 E.2.1 Modes of Operation .......................................................................................................... 262 E.2.2 Talkgroup and Channel Selection...................................................................................... 262 E.2.3 Special-Purpose Subscribers Modes of Operation............................................................ 263 E.2.4 Frequency Band (Single-Band Subscribers) ...................................................................... 263 E.2.5 Frequency Band (Multi-Band Subscribers) ....................................................................... 263 E.2.6 Push-To-Talk Identification ............................................................................................... 263 E.2.7 Seamless Roaming ............................................................................................................ 263 E.2.8 Out-Of Range Notification ................................................................................................ 264 E.2.9 Fallback Mode ................................................................................................................... 264 E.2.10 Site Trunking Mode ........................................................................................................... 264 E.2.12 Individual Unit Alert and Individual Call............................................................................ 265 E.2.13 Scan and Priority Scan ....................................................................................................... 265 E.2.14 Optional Over-the-Air Programming ................................................................................ 265 Section E.2 Response Form ................................................................................................................... 266 E.3 Encryption ................................................................................................................................. 268 Section E.3 Response Form ................................................................................................................... 269 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona E.4 12030-RFP P25 Radio System Infrastructure Upgrade Requirements for Portable Subscriber Radio Equipment ......................................................... 270 E.4.1 Requirements Common to All Portables .......................................................................... 270 E.4.2 Types of Portables............................................................................................................. 271 Section E.4 Response Form ................................................................................................................... 277 E.5 Requirements for Mobile Subscriber Radio Equipment ........................................................... 281 E.5.1 Requirements Common to All Mobiles ............................................................................. 281 E.5.2 Types of Mobiles ............................................................................................................... 282 Section E.5 Response Form ................................................................................................................... 287 E.6 Requirements for Control Station Subscriber Radio Equipment .............................................. 291 E.6.1 Requirements Common to All Control Stations ................................................................ 291 E.6.2 Types of Control Stations .................................................................................................. 291 Section E.6 Response Form ................................................................................................................... 293 Appendix 1 - Defined Areas With Special Coverage Requirements .......................................................... 295 Appendix 2 - Antenna Sites Currently In Use ............................................................................................ 317 Appendix 3 - Diagram of Existing County Microwave Network ................................................................ 319 Appendix 4 - List of Shape Files Provided ................................................................................................. 321 Appendix 5 - Standards for Grounding and Lightning and Transient Suppression ................................... 325 Appendix 6 - Requirements and Procedures for Radio Coverage Verification Acceptance Testing......... 336 Appendix 7 - Requirements and Procedures for Ninety-Day Reliability Testing ...................................... 340 Appendix 8 - Construction Requirements for Buildings Built On-Site ...................................................... 342 Appendix 9 - Cabling Specification for Data Center Environments .......................................................... 346 Appendix 10 - County Subscriber Radio Inventory ................................................................................... 378 Appendix 11 - Non-County Subscriber Radio Inventory ........................................................................... 386 Appendix 12 - Definition of Acronyms Used in This Document................................................................ 390 Appendix 13 - Map of County-Owned Parcels .......................................................................................... 396 Appendix 14 – Existing TDM Circuits for Telephone and Data ................................................................. 398 May 17, 2012 Document 2 - Specification & Response Document Table of Contents Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SECTION A - DEFINITIONS USED IN THIS DOCUMENT A.1 The word "County" shall mean the governmental entity known as the County of Maricopa, Arizona and all of its agencies and departments. A.2 The term "Radio System" shall mean all equipment and materials that are part of the completed infrastructure that is described in this document, including optional items that are ultimately purchased by the County. A.3 The term "Project" shall mean the totality of all materials and all work necessary to provide to the County a complete, turnkey Radio System, meeting or exceeding all requirements of this RFP and functional in all respects. The term "Project" shall include Warranties, but shall not include Optional Post-Warranty Maintenance or purchases of Subscriber Radio Equipment. A.4 The word "Contract" shall mean the contract resulting from this RFP, including all Warranties, Optional Post-Warranty Maintenance and purchase of Subscriber Radio Equipment. A.5 The term "Subscriber Radio Equipment" or "Subscriber Radio(s)" or "Subscriber(s)" shall mean portable, mobile and control station radio equipment operated by end-users. A.6 The word "capable" or the words "capable of" shall mean that the subject equipment or component may be programmed or equipped for the feature or function at a later date, without the purchase of additional hardware, but the purchase of additional software or firmware may be required. A.7 The word "equipped" shall mean that the subject equipment or component shall have the feature or function already programmed, configured and available for use at the time of initial delivery. A.8 The word "Respondent" shall mean the company or individual responding to this RFP. A.9 The word "Contractor" shall mean the Respondent that is selected and awarded the contract that results from this RFP. A.10 The term "equipment space" shall mean a shelter, building, enclosure, outdoor cabinet, room, or other location where Radio System equipment or components may be located. A.11 The word "Site" shall mean any location where Radio System equipment and components will be installed or Project work will be performed. A.12 The word "Antenna Site" shall mean any site where Trunked/LMR or microwave RF transmitting and/or receiving equipment will be installed. A.13 The term "User Agency" and "User Agencies" shall mean agencies and departments of the County and other non-County entities that are authorized to use the Radio System. A.14 The term "environmental control system(s)" shall mean air conditioners, heaters, heat pumps, humidifiers, de-humidifiers, ventilation fans, filters and all other equipment used to control temperature, humidity and/or the accumulation of dust, dirt and air pollutants within an equipment space. May 17, 2012 Document 2 - Specification & Response Document Page 1 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade A.15 The term "Proposal" shall mean the Respondent's complete document submitted in response to this RFP. A.16 The word "optional" shall mean the item shall be purchased at the County's discretion, but the Respondent/Contractor is required to provide a firm, fixed price for the item. The optional item shall be priced separately and not as part of another item. A.17 The term "Final Acceptance" shall mean the acceptance by the County of the complete, fully functional Radio System after all of the criteria stated in Section C.13 have been met. A.18 The term "Beneficial Use" shall mean the normal operational use of the Radio System or a portion of the Radio System by the County prior to Final Acceptance of the Radio System by the County. A.19 Definitions of the acronyms used in this document are contained in Appendix 12. May 17, 2012 Document 2 - Specification & Response Document Page 2 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications RFP Section: 12030-RFP, Document 2, Sections A.1 – A.19 No Response Required {End Section A} May 17, 2012 Document 2 - Specification & Response Document Page 3 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SECTION B - OVERVIEW OF EXISTING RADIO SYSTEM B.1 General The existing radio system currently in use by Maricopa County is a fifteen-site (multicast only), Project 16, 800 MHz trunked radio system. It is a hybrid analog/digital system, using Motorola's proprietary SmartZoneTM technology with a 3600 bps control channel. Talkgroups may be designated as analog or digital. Digital talkgroups utilize the Project 25 Common Air Interface. B.2 Controller The current trunking central controller is Motorola software revision 7.11 using a local redundant central controller. SmartXTM boxes are utilized at the central controller site for compatibility with existing QuantarTM repeaters and Centracom Gold Elite dispatch consoles. Additional information can be found in Document 3 of this RFP, the Confidential Supplement. B.3 Coverage The existing radio system covers approximately 42 percent of the geographic area of Maricopa County at DAQ 3.4, 95% reliability. B.3.1 Please see Appendix 2 for a listing of existing antenna sites. B.3.2 Maricopa County radio engineers have measured 6dB of degradation to their 800 MHz receivers at the White Tanks East site due to high radio frequency ("RF") noise levels. B.4 Encryption Certain talkgroups used by the Maricopa County Sheriff's Office ("MCSO") and Adult Probation are encrypted, using DES-OFB encryption. Keys are manually loaded into each radio using a Key Variable Loader ("KVL"). Over-the Air Rekeying ("OTAR") is not used. B.5 Dispatch Centers B.5.1 Sheriff's Dispatch Center B.5.1.1 The existing Sheriff's dispatch center is equipped with ten Motorola Centracom Gold Elite dispatch consoles. May 17, 2012 B.5.1.2 The existing dispatch center will be replaced in the summer of 2013. The new dispatch center will have twenty-eight dispatcher/calltaker positions. All of the positions will be cabled for radio dispatch consoles, however only sixteen will actually be equipped with a radio dispatch console. B.5.1.3 The existing dispatch center is equipped with two NICE Systems NiceLog NL-2000 logging recorders. A list of the talkgroups and channels being recorded can be found in Document 3 of this RFP, the Confidential Supplement. B.5.1.4 Additional information about the Sheriff's existing and new dispatch centers can be found in Document 3 of this RFP, the Confidential Supplement. Document 2 - Specification & Response Document Page 4 of 399 Maricopa County, Arizona B.5.2 B.6 12030-RFP P25 Radio System Infrastructure Upgrade Adult Probation Dispatch Center B.5.2.1 The existing dispatch center is equipped with nine Motorola Centracom Gold Elite dispatch consoles. B.5.2.2 The existing dispatch center is equipped with one NICE Systems NiceLog NL-2000 logging recorder. B.5.2.3 Additional information about the Adult Probation dispatch center can be found in Document 3 of this RFP, the Confidential Supplement. B.5.3 Animal Care and Control Dispatch Center The existing primary dispatch center is located at 2500 S. 27th Avenue in Phoenix (part of the Durango Complex). The existing dispatch center is equipped with two Motorola Centracom Gold Elite dispatch consoles. There are also two control stations used as backup. One console position is always manned, the second is used during periods of heavy traffic. There are also four additional control stations in other offices at this location. A backup dispatch center is located at 2630 W. 8th Street in Mesa, and is equipped with a control station. B.5.4 Flood Control District Alert Operations Center The Flood Control District's Alert Operations Center ("AOC") is located at 2801 W. Durango Street in Phoenix (part of the Durango Complex). It is equipped with one Motorola Centracom Gold Elite console. The AOC is manned during flood events, and collects data from remote rain gauges and personnel in the field. This data is transmitted to the Maricopa County Department of Transportation and the Emergency Operations Center in the form of flood warnings, and made available to the general public through the Flood Control District's web site. B.5.5 Maricopa County Department of Transportation The Maricopa County Department of Transportation ("MCDOT") dispatch center is located at 2901 West Durango Street in Phoenix (part of the Durango Complex). It is equipped with two Motorola Centracom Gold Elite consoles. The dispatch center is manned during normal business hours only. B.5.6 OET Wireless Systems Division The OET Wireless Systems Division has one Centracom Gold Elite console at their location to facilitate system maintenance and troubleshooting. Interoperability With Other Regional Radio Networks B.6.1 There are no existing system-to-system electronic interfaces. B.6.2 May 17, 2012 Interoperability talkgroups for the Regional Wireless Cooperative ("RWC") and the Topaz Regional Wireless Cooperative ("TRWC") are programmed into the subscriber radio units. RWC interoperability talkgroups are programmed into the G and H zones of the subscriber radios. The G-zone talkgroups are clear, the H-zone talkgroups are encrypted. TRWC interoperability talkgroups are programmed into the V and W zones on the subscriber radios. The V-zone talkgroups are clear, the W-zone talkgroups are Document 2 - Specification & Response Document Page 5 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade encrypted. The Y-zone and possible the Z-zone are reserved for Maricopa County interoperability talkgroups. Currently there are no Y or Z-zone talkgroups defined by the County. B.7 B.6.3 The Arizona Interoperable Radio Network ("AIRS") conventional interoperability radio channels (800 MHz only) are also programmed into the County's subscriber radios, but they are rarely used. The Sheriff's Dispatch Center has the capability to transmit and receive on the 800 MHz, UHF and VHF High Band AIRS channels through their dispatch consoles. The control stations are located in the penthouse of the dispatch center building. B.6.4 The Sheriff's Dispatch Center has the capability to transmit and receive on the Emergency Management VHF Low Band simplex channel 47.66 MHz through their dispatch consoles. The base station is located in the penthouse of the dispatch center building. B.6.5 The Sheriff's Dispatch Center has the capability to transmit and receive on the RWC PSAP Call and PSAP Patch talkgroups through their dispatch consoles. The control stations are located in the penthouse of the dispatch center building. B.6.6 The Sheriff's Dispatch Center has the capability to transmit and receive on the air-toground frequency 123.1 MHz through their dispatch consoles. The base station is located at Thompson Peak. B.6.7 The Sheriff's Dispatch Center has the capability to transmit and receive through their dispatch consoles on control stations (a primary and a backup) that communicate with the Palo Verde Nuclear Generating Station's radio communications system in the event of an emergency. The control stations are located in the penthouse of the dispatch center building. B.6.8 The Sheriff's Dispatch Center has the capability to transmit and receive on the 800 MHz 8CALL90 national interoperability channel through their dispatch consoles. The control station is located in the penthouse of the dispatch center building. B.6.9 The County has reached an agreement with RWC, TRWC and the Yuma Regional Communications System ("YRCS") to assign four trunked talkgroups per system for interoperability purposes. These four talkgroups will be bridged between the systems using an analog audio bridge being supplied and installed by others. The equipment has not yet been installed. Emergency Consoles at Jails The nine Maricopa County jails are equipped with consoles that monitor the trunked system control channel and alert jail control center personnel when a Detention Officer presses the emergency ("EM") button on their subscriber radio. The current configuration uses a Motorola Site Lens terminal connected to a control station configured to monitor trunked control channel activity. When an EM is received, the console presents an audible and a visual alert to the officers at the jail control center and displays the PTT ID and PTT ID alias of the subscriber May 17, 2012 Document 2 - Specification & Response Document Page 6 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade initiating the emergency. The audible and visual alerts can be silenced, the alert acknowledged and the emergency cleared through the Emergency Console. The current consoles are compatible with the Motorola SmartZone 3600 bps control channel, but are not compatible with the Project 25 trunking control channel. B.7.1 Each jail is equipped with two Emergency Consoles, one for its own EMs and one to monitor EMs from another jail, as backup. B.8 Call Boxes Maricopa County operates fourteen call boxes which are available for use by the general public in certain designated recreational areas to contact the Sheriff's dispatcher to report a crime or other emergency. The heart of the call box is a trunked portable radio. When the "call" button is pressed, the call box sends an alert to the dispatcher that identifies the call box. The dispatcher then enters the ID of the call box into the control unit which sends a message to the call box activating it and enabling the PTT button. The dispatcher and the reporting party may then have a two-way PTT conversation. When the call is finished, the dispatcher deactivates the call box and it returns to a "ready" state. Over two thousand calls per year are placed through the call box network. B.9 Bi-Directional Amplifiers Nine buildings are equipped with Bi-Directional Amplifiers ("BDAs") to provide coverage within the buildings. The BDAs operate in the 806 MHz - 869 MHz band only. The following buildings have BDAs: B.10 B.9.1 Fourth Avenue Jail, 201 S. Fourth Avenue, Phoenix B.9.2 Estrella Jail, 2939 W. Durango St., Phoenix B.9.3 Lower Buckeye Jail, 3250 W. Lower Buckeye Rd., Phoenix B.9.4 Durango Jail, 3225 W. Gibson Lane, Phoenix B.9.5 First Avenue Jail, 102 W. Madison St., Phoenix B.9.6 Madison Avenue Jail, B.9.7 Towers Jail, 3127 W. Gibson Lane, Phoenix B.9.8 Central Courts Complex, downtown Phoenix (which includes the Central Courts Building at 201 W. Jefferson, the East Court Building at 101 W. Jefferson, and the West Court Building, 111 S. Third Avenue) B.9.9 South Court Tower, 175 W. Madison, Phoenix Subscriber Radio Inventory B.10.1 An inventory of the County's mobile, portable and control station radio equipment is contained in Appendix 10. An inventory of subscriber radio equipment used by NonCounty agencies is contained in Appendix 11. B.10.2 The County is engaged in a program of regular replacement of its subscriber radio fleet. The County recently issued a contract to its incumbent vendor, Motorola, for the May 17, 2012 Document 2 - Specification & Response Document Page 7 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade purchase of several thousand new subscriber radios. When this contract is complete, all subscriber radios in the County's fleet will be equipped for P25 Phase 1 (FDMA) operation. However, approximately half of the fleet will not be capable of P25 Phase 2 (TDMA) operation. Over the course of this Project, the County intends to make additional purchases of subscriber radios from the Contractor to replace the radios in its current fleet that are not capable of P25 Phase 2, and to make additional purchases of subscriber radios from the Contractor over the life of the Radio System. B.10.2.1 Section C.5.2 describes the expected time frame for purchases of additional subscriber radio equipment. B.11 800 MHz Rebanding The County has executed a Planning Funding Agreement ("PFA") with Sprint-Nextel for the rebanding of the current 800 MHz radio system. Details of that PFA will be disclosed to the Contractor following contract award. B.12 Backhaul The backhaul for the County's existing radio system utilizes a six-site microwave OC-3 ring as its core. Spurs to the remaining radio system antenna sites are 11 GHz and 21 GHZ microwave with between 4 DS-1 and 12 DS-1 capacity. The backhaul system primarily supports the existing radio system, but a small amount of other data, including telephone circuits, is provided to County facilities in outlying areas. Additional details of the existing backhaul system are contained in Appendix 3 and in Document 3, Confidential Supplement. B.13 Backup Data Center The County operates a backup data center that is currently connected to other County facilities through a fiber-optic network (see Document 3 - Confidential Supplement for details). The building also has facilities for a future connection via microwave. If requested by the Contractor, the County will supply a rooftop mount for up to two microwave antennas and space for microwave transceivers. A cable raceway runs from the roof to a separate RF equipment room that is in the same building but not co-located within the County's backup data center. The County will also provide access to conduit(s) between the backup data center and the RF equipment room at the request of the Contractor. May 17, 2012 Document 2 - Specification & Response Document Page 8 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications RFP Section: 12030-RFP, Document 2, Sections B.1 – B.12 No Response Required {End Section B} May 17, 2012 Document 2 - Specification & Response Document Page 9 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SECTION C - SCOPE OF WORK The Contractor shall provide all materials and perform all services necessary to provide to the County a complete, turnkey Radio System, meeting or exceeding all requirements of this RFP and functional in all respects. Work to be performed by the Contractor shall include, but not be limited to: C.1 Project Management C.1.1 The overarching goal of the Contractor, and of the Contractor's staff and of all subcontractors shall be to complete the work of the Project and to meet or exceed the requirements of this RFP in an expeditious manner and without subordinating quality, cost or schedule. C.1.2 Under the direction of the County, the Contractor shall manage the work of the Project, including the work of all subcontractors. C.1.3 The Contractor shall prepare a complete plan and analysis of all Project work ("Project Plan"), which shall be approved by the County prior to the start of construction or installation work. See Section C.1.6. C.1.4 The Contractor shall execute the work of the project in accordance with the approved Project Plan. The Contractor shall not deviate from the approved Project Plan without the prior written approval of the County, and the Project Plan shall be immediately modified to reflect the approved changes. C.1.5 Contractor's Project Manager C.1.5.1 The Contractor shall designate a member of its staff as its Project Manager. The Contractor's Project Manager ("CPM") shall be responsible for execution of the approved Project Plan. C.1.5.2 The CPM shall be a full-time employee of the Contractor and shall be assigned to the Project on a full-time basis. C.1.5.3 The CPM shall have sufficient authority to make decisions on behalf of the Contractor for Project-related issues. C.1.5.4 The CPM shall direct the activities of the Contractor and its Subcontractors, prepare weekly project status reports for presentation to the County, and shall hold project status meetings between the Contractor, the County and other key stakeholders at least monthly. The CPM shall conduct meetings, both formal and informal, with designated County Project staff members as often as is necessary to expeditiously complete the Project. C.1.5.5 The CPM shall be the County's primary point of contact for all Projectrelated issues. C.1.5.5.1 May 17, 2012 The Contractor shall provide CPM contact information to the County so that the County may contact the CPM Document 2 - Specification & Response Document Page 10 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade on a 24-hour, 7 day per week basis. The County will endeavor to limit calls after normal business hours to emergencies only. C.1.5.6 C.1.6 May 17, 2012 The CPM shall reside within 75 miles of Phoenix, Arizona for the duration of the Project. Project Plan The Project Plan shall be prepared in accordance with the guidelines contained in the Project Management Body of Knowledge ("PMBOK") published by the Project Management Institute, Newtown Square, PA. The Project Plan shall contain but not be limited to the following: C.1.6.1 A Detailed Design Document describing how the equipment will be installed, connected and tested. See Section C.2.1 of this document. C.1.6.2 A detailed list of all materials to be used as part of the Project (including materials provided by the County, if any, the Contractor, Subcontractors, utilities and any other source). The materials list shall include but not be limited to all components, optional sub-components (example: modems and other cards that are part of a channel bank), optional features or programming, software, cables, connectors and maintenance and operating manuals. C.1.6.3 A Work Breakdown Structure ("WBS") of all tasks and sub-tasks to be performed as part of the Project. C.1.6.4 A written description, based on the WBS, of all tasks and sub-tasks to be performed and by whom they are to be performed (Contractor, subcontractor, the County or others). Any work, utilities or other materials or services that the County has agreed to provide shall be identified. C.1.6.5 A detailed Project Schedule, in Gantt-chart format, developed using Microsoft Project software, based on the WBS, indicating: C.1.6.5.1 Schedule and cost baselines; C.1.6.5.2 Delivery dates for materials and other deliverables; C.1.6.5.3 Start and end dates for the tasks and sub-tasks to be performed; C.1.6.5.4 Dates of Project milestones; C.1.6.5.5 Entity or individual assigned the responsibility for completion of the work; C.1.6.5.6 The Project Schedule shall highlight tasks that are part of the critical path; Document 2 - Specification & Response Document Page 11 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade C.1.6.5.7 C.1.6.6 An Impact Analysis describing how the Project work will impact the normal communications (including the existing microwave system) of the County. C.1.6.6.1 Due to the life-safety nature of the County’s radio communications, the Contractor shall make every effort to avoid situations where a communications outage is necessary to complete Project work. C.1.6.6.2 Any work that may result in a communications outage or in interference to the County's current communications must be kept to an absolute minimum. C.1.6.7 A Training Plan. The Training Plan shall specify the training that will be required by the County to properly operate, maintain and care for the Radio System. Refer to Section D.28 of this Specification for training requirements. C.1.6.8 A Cutover Plan for commissioning the Radio System and placing it in normal daily operation, the programming of Subscriber Radio Equipment, transitioning the radio users to the Radio System in such a way that there is no loss of radio communications during the transition period, decommissioning any existing radio equipment that is to be removed and disposal of the decommissioned equipment. Detailed requirements for Commissioning, Migration and De-Commissioning are contained in Section D.29 of this document. C.1.6.9 A Risk Management Plan. The Risk Management Plan shall identify potential problems and issues that could stop or significantly delay the Project or that may necessitate additional unplanned materials, personnel or other resources. C.1.6.9.1 C.1.6.10 The Risk Management Plan shall identify contingency plans to eliminate or reduce the impact of the problems and issues identified. A Quality Plan. The Quality Plan shall conform to the requirements of Section D.2.1. The Quality Plan shall: C.1.6.10.1 May 17, 2012 The Project Schedule shall also clearly identify any work that may result in a radio communications outage or in interference to the County's current radio communications; Define the person(s) responsible for Project quality assurance, the standards and procedures that will be Document 2 - Specification & Response Document Page 12 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade used, and resources required to conduct quality-related activities for the Project. C.1.6.10.2 Define acceptance test plans and procedures and describe acceptance criteria for deliverables as they will be used in acceptance testing, C.1.6.10.3 Specify relevant quality standards, C.1.6.10.4 Define the Quality Assurance activities for the Project, C.1.6.10.5 Define how variance(s) from acceptable criteria will be reported and resolved, C.1.6.10.6 Define the quality monitoring and reporting processes. C.1.6.11 A Communications Plan. The Communications Plan shall describe in detail the types of communications that will occur as part of this Project (examples: status reports, engineering submittals), the stakeholders to whom the communications will be directed, the communications medium to be used, and responses required. C.1.6.12 A Safety Plan. The Safety Plan shall comply with the requirements of Section D.3, and shall describe in detail the means by which the safety of humans and property will be ensured. C.1.6.12.1 C.1.7 May 17, 2012 The Safety Plan shall clearly state how the requirements of all applicable laws, regulations and codes, particularly OSHA Regulations and other requirements stated in this RFP, shall be met. C.1.6.13 An Issue Log. The Issue Log shall provide a mechanism for organizing, maintaining, and tracking of issues that require a decision or further investigation. C.1.6.14 A schedule of invoicing for payment for work performed or milestones achieved. The schedule shall reflect the terms of the contract between the Contractor and the County. This schedule may be incorporated with the Project Schedule if desired. Work Locations C.1.7.1 CPM, Engineering Manager/Lead Engineer and Site Construction Manager(s) primary work location shall be at the Durango Complex. C.1.7.1.1 Additional project staff may be permanently or temporarily located at the Durango Complex at the Contractor's discretion. C.1.7.1.2 All Project staff shall be required to perform tasks including but not limited to investigations, studies, Document 2 - Specification & Response Document Page 13 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade documentation, surveys, supervision and inspections at locations in the field on an as-needed basis. C.1.7.2 C.1.8 C.1.7.2.1 Trailer(s) shall be placed at the Durango Complex at a location to be specified by the County. C.1.7.2.2 Trailer(s) shall incorporate heating, air conditioning, plumbing and restroom facilities adequate for the expected number of staff plus two consultants to be designated by the County. Contractor's Project Staff C.1.8.1 The County shall review and approve the Contractor's proposed staff, including that of all subcontractors, prior to their engagement. C.1.8.2 May 17, 2012 Contractor shall provide construction trailer(s) suitable as a Project Office for its staff, plus two consultants to be selected by the County. The County shall have the right to reject or bar any individual at any time, without cause and for any reason. Document 2 - Specification & Response Document Page 14 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.1 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Example of 12030-RFP, Document 2, Section C.1 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Exception Comply Comply Standard 3rd Party 3rd Party Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section/ Exception Subsection C.1 C.1.1 C.1.2 C.1.3 C.1.4 C.1.5 C.1.5.1 C.1.5.2 C.1.5.3 C.1.5.4 C.1.5.5 C.1.5.5.1 C.1.5.6 C.1.6 C.1.6.1 C.1.6.2 C.1.6.3 C.1.6.4 C.1.6.5 C.1.6.5.1 C.1.6.5.2 C.1.6.5.3 C.1.6.5.4 C.1.6.5.5 C.1.6.5.6 C.1.6.5.7 C.1.6.6 C.1.6.6.1 C.1.6.6.2 C.1.6.7 C.1.6.8 C.1.6.9 May 17, 2012 Document 2 - Specification & Response Document Page 15 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Example of 12030-RFP, Document 2, Section C.1 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Standard Standard Requirement Comply/ Section/ Exception Subsection C.1.6.9.1 C.1.6.10 C.1.6.10.1 C.1.6.10.2 C.1.6.10.3 C.1.6.10.4 C.1.6.10.5 C.1.6.10.6 C.1.6.11 C.1.6.12 C.1.6.12.1 C.1.6.13 C.1.6.14 C.1.7 C.1.7.1 C.1.7.1.1 C.1.7.1.2 C.1.7.2 C.1.7.2.1 C.1.7.2.2 C.1.8 C.1.8.1 C.1.8.2 {End Section C.1} May 17, 2012 Document 2 - Specification & Response Document Page 16 of 399 Maricopa County, Arizona C.2 12030-RFP P25 Radio System Infrastructure Upgrade Design and Engineering The Contractor shall design and implement the Radio System to be in compliance with the requirements and specifications stated in this document. The Contractor shall provide all necessary engineering to design and implement the Radio System. The Contractor shall prepare schematic diagrams, physical microwave path surveys, rack elevation drawings, structural analyses, geotechnical and soil composition reports, site plans, construction drawings and all other design and engineering documents that are necessary. All design and engineering documents shall be of sufficient detail so that the County may determine compliance to codes, laws, regulations, ordinances and the requirements of this RFP. All designs, plans, specifications, analyses and reports shall be approved by the County prior to start of the subject work. C.2.1 Detailed Design Document The detailed Radio System design shall be placed into a Detailed Design Document that shall become part of the Project Plan described above. The system Detailed Design Document shall contain, at a minimum: C.2.1.1 A complete block diagram of the entire Radio System; C.2.1.2 Diagrams showing the interconnection of components at and between each equipment installation location, the Dispatch Centers and any other location where Project work will be performed; C.2.1.3 Floor plan diagrams and rack layouts for each equipment installation location showing the planned physical locations of the new equipment; C.2.1.4 Detailed power and HVAC requirements for each equipment installation location; C.2.1.5 A ground system and transient suppression plan for each Site; C.2.1.6 A complete Bill of Materials, including manufacturer, model and included options of each component and a complete list of accessories, cables and ancillary hardware being provided; C.2.1.7 A detailed backhaul plan of the entire Radio System showing how signals to and from each Site will be routed within the Radio System and the bandwidth required, including: C.2.1.8 May 17, 2012 C.2.1.7.1 Identification of network segments that will be fiber optic C.1.2.7.2 For microwave, exact transmit frequencies shall be specified if known, otherwise the frequency band shall be specified for each link C.1.2.7.3 Details of network timing and synchronization A frequency assignment plan specifying exact transmit frequencies for each Antenna Site; Document 2 - Specification & Response Document Page 17 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade C.2.1.9 An intermodulation analysis and Radio Frequency Noise/Receiver Degradation analysis of each antenna site, taking into consideration the Radio System transmit and receive frequencies and the frequencies of other RF sources and receivers that may be present. C.2.1.10 Detailed descriptions of the proposed antenna systems at each site, taking into account the results of the intermodulation analysis and Radio Frequency Noise/Receiver Degradation Analysis described above. C.2.1.11 Computerized modeling of the radio coverage that will be obtained from the completed Radio System, in the form of Coverage Maps. C.2.1.12 C.2.1.11.1 These Coverage Maps shall become the basis for the Radio Coverage Verification Acceptance Test. C.2.1.11.2 Coverage Maps shall comply with the requirements of Section C.2.2 of this document. Details of the microwave path design for each microwave link in sufficient detail that a competent telecommunications engineer may independently validate compliance with specifications, FCC rules and best industry practices; C.2.1.12.1 C.2.1.13 A Failure Mode Analysis describing the impact to end users and operations and maintenance personnel when key components of the Radio System fail. C.2.1.13.1 C.2.2 May 17, 2012 Copies of physical path surveys and frequency coordination documents shall be included. The Failure Mode Analysis shall describe the steps that must be taken to restore the system to normal operation. Requirements for Coverage Maps These requirements shall apply to all Coverage Maps produced for this Project, including the Coverage Maps presented as part of the Respondent's proposals. Please refer to the definitions and other information contained in Section D.20 "Trunked/LMR Subsystem RF Coverage Requirements." C.2.2.1 The Respondent/Contractor shall perform computerized modeling of the radio coverage that will be obtained from the completed Radio System. C.2.2.2 The results of the computerized modeling shall be in graphic form, overlaid onto maps of Maricopa County and the surrounding area, which shall include highways, major streets, County Parks, major County buildings and major landmarks. Document 2 - Specification & Response Document Page 18 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade C.2.2.3 A "single site map" shall show the coverage (either talkout or talkback) obtained from a single site. C.2.2.4 A "composite map" shall show the coverage obtained (either talkout or talkback) from a specific grouping of sites, such as all the sites in a simulcast cell. C.2.2.5 Paper Coverage Maps shall be printed in ANSI E size in order to provide a sufficient level of detail. C.2.2.5.1 C.2.2.6 C.2.2.7 May 17, 2012 Copies of Coverage Maps may be printed in smaller sizes if desired. The following coverage maps shall be required for the Respondent's proposal and the Detailed Design Document: C.2.2.6.1 Composite maps (one for talkout and one for talkback) showing the Portable Coverage that will be obtained from all the antenna sites. C.2.2.6.2 Composite maps (one for talkout and one for talkback) for each Defined Area showing where signal levels 6 dB greater than that required for Portable Coverage will be obtained from all the antenna sites serving the Defined Area. C.2.2.6.3 Composite maps (one for talkout and one for talkback) for each Defined Area showing where signal levels 12 dB greater than that required for Portable Coverage will be obtained from all the antenna sites serving the Defined Area. C.2.2.6.4 Composite maps (one for talkout and one for talkback) for the area defined as Government Center showing where signal levels 18 dB greater than that required for Portable Coverage will be obtained from all the antenna sites serving the Defined Area. Additional coverage maps that will be required only for the Detailed Design Document: C.2.2.7.1 Single site maps (one for talkout and one for talkback) for each individual antenna site showing the Portable Coverage that will be obtained for each site. C.2.2.7.2 Composite maps (one for talkout and one for talkback) showing the Portable Coverage that will be obtained from each simulcast cell. Document 2 - Specification & Response Document Page 19 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade C.2.2.8 The Coverage Maps shall account for typical body-shielding effects and shall also account for additional signal attenuation due to land-use. C.2.2.9 The Coverage Maps shall account for areas of simulcast distortion. C.2.2.10 A data sheet in written form shall be provided with each Coverage Map and shall contain the following information: C.2.2.11 C.2.2.10.1 Transmitter output power for each transmitter C.2.2.10.2 Transmitter combining and filtering losses for each transmitter C.2.2.10.3 Coaxial cable manufacturer, type and length for each antenna losses for connectors and losses for coaxial cable jumpers C.2.2.10.4 Manufacturer, model, gain (in dBd), height above ground, azimuth (if directional) and downtilt of each antenna C.2.2.10.5 Gain of each Tower-Top Amplifier ("TTA") C.2.2.10.6 Gain or loss of each receiver multicoupler C.2.2.10.7 Faded sensitivity (per TSB-88) of each receiver C.2.2.10.8 Portable radio faded receiver sensitivity (per TSB-88) C.2.2.10.9 Portable radio transmitter output power C.2.2.10.10 Gain or loss (in dBd) of the portable radio antenna C.2.2.10.11 Losses assumed for body-shielding effects C.2.2.10.12 Losses assumed for land use and land clutter C.2.2.10.13 Simulcast delay threshold criteria C.2.2.10.14 Any other criteria or parameters used in the preparation of the map. In addition to the Coverage Map itself, the coverage for each map shall be provided in the form of a digital shape file, in ArcView format, referenced to latitude and longitude. C.2.2.11.1 C.2.2.12 May 17, 2012 The shape file(s) shall be provided along with the printed maps on a CD-ROM or DVD-ROM. The coverage displayed on each map shall not be truncated or limited by political borders, jurisdictional areas, the borders of any Defined Area or any other artificial limit. All coverage that meets the required coverage criteria shall be displayed out to the limits of each map. Document 2 - Specification & Response Document Page 20 of 399 Maricopa County, Arizona C.2.2.13 C.2.3 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade The Coverage Maps described above shall be used exclusively for determination of radio coverage as will be experienced by the end users, and shall be completely separate and in addition to any maps produced for frequency coordination and FCC licensing purposes. Architecture, Surveying and Civil, Structural, Electrical and Mechanical Engineering The Contractor shall perform Architecture, Surveying and Civil, Structural, Electrical and Mechanical Engineering as required to complete the Project work. Requirements for Civil, Structural, Electrical and Mechanical Engineering are found in Section D of this document. Document 2 - Specification & Response Document Page 21 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.2 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.2 Requirement Comply/ Section Exception Standard/ Custom/ 3rd Party (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply (Choose one) Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard C.2 C.2.1 C.2.1.1 C.2.1.2 C.2.1.3 C.2.1.4 C.2.1.5 C.2.1.6 C.2.1.7 C.2.1.7.1 C.2.1.7.2 C.2.1.7.3 C.2.1.8 C.2.1.9 C.2.1.10 C.2.1.11 C.2.1.11.1 C.2.1.11.2 C.2.1.12 C.2.1.12.1 C.2.1.13 C.2.1.13.1 C.2.2 C.2.2.1 C.2.2.2 C.2.2.3 C.2.2.4 C.2.2.5 C.2.2.5.1 C.2.2.6 C.2.2.6.1 C.2.2.6.2 May 17, 2012 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Document 2 - Specification & Response Document Page 22 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.2 Requirement Comply/ Section Exception Standard/ Custom/ 3rd Party (Choose one) Comply Comply (Choose one) Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard C.2.2.6.3 C.2.2.6.4 C.2.2.7 C.2.2.7.1 C.2.2.7.2 C.2.2.8 C.2.2.9 C.2.2.10 C.2.2.10.1 C.2.2.10.2 C.2.2.10.3 C.2.2.10.4 C.2.2.10.5 C.2.2.10.6 C.2.2.10.7 C.2.2.10.8 C.2.2.10.9 C.2.2.10.10 C.2.2.10.11 C.2.2.10.12 C.2.2.10.13 C.2.2.10.14 C.2.2.11 C.2.2.11.1 C.2.2.12 C.2.2.13 C.2.3 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. {End Section C.2} May 17, 2012 Document 2 - Specification & Response Document Page 23 of 399 Maricopa County, Arizona C.3 12030-RFP P25 Radio System Infrastructure Upgrade Licensing and Permitting C.3.1 FCC Licenses The Contractor shall secure new 700 MHz FCC licenses for the County as required by the design of the new Radio System, and, if required, modify the County's 800 MHz licenses to reflect the design of the Radio System and secure new 800 MHz frequencies. The Contractor shall also modify the County's existing microwave licenses and secure for the County new licenses as required by the design of the backhaul network. The Contractor shall prepare license and frequency coordination applications, engineering studies (if required) and all other necessary supporting documentation, and present these documents to the County for signature. Following signature of the documents, the Contractor shall submit them to the proper authorities and track the progress of the application, submitting additional supporting documentation if required, until the final licenses are granted. C.3.1.1 C.3.2 The Contractor shall account for frequency changes necessitated by the FCC's 800 MHz rebanding mandate. FAA Clearances C.3.2.1 For any site where new tower construction will occur or the height of an existing tower will be increased, the Contractor shall file a "Notice of Proposed Construction or Alteration" (form 7460-1) with the Federal Aviation Administration ("FAA"). C.3.2.2 The Contractor shall incorporate into its Radio System design any requirements imposed by the FAA. C.3.2.3 Where required by the FAA, the Contractor shall also file a "Notice of Actual Construction" (form 7460-2) with the FAA immediately upon completion of construction work. C.3.3 Antenna Structure Registration For sites that are required to obtain FCC Antenna Structure Registration, the Contractor shall prepare and file the necessary documents on behalf of the County. C.3.4 Zoning Variances See Section D.5, "Site Acquisition Assistance". C.3.5 Construction Permits The Contractor shall obtain any and all necessary environmental permits, construction permits and construction code inspections from the authorities having jurisdiction, at the Contractor's sole cost and expense. C.3.6 Environmental Permits See Section D.6. May 17, 2012 Document 2 - Specification & Response Document Page 24 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.3 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.3 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Standard Requirement Comply/ Section Exception C.3 C.3.1 C.3.1.1 C.3.2 C.3.2.1 C.3.2.2 C.3.2.3 C.3.3 C.3.4 C.3.5 C.3.6 {End Section C.3} May 17, 2012 Document 2 - Specification & Response Document Page 25 of 399 Maricopa County, Arizona C.4 12030-RFP P25 Radio System Infrastructure Upgrade Site Acquisition Assistance The Contractor shall assist the County in the acquisition of property, acquisition of easements, acquisition of leases, variances to zoning and acquisition of all other agreements necessary to construct or modify antenna sites or other facilities that are to be a part of the Radio System. The required assistance described more fully in Section D.5 of this RFP. May 17, 2012 Document 2 - Specification & Response Document Page 26 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.4 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.4 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception C.4 {End Section C.4} May 17, 2012 Document 2 - Specification & Response Document Page 27 of 399 Maricopa County, Arizona C.5 12030-RFP P25 Radio System Infrastructure Upgrade Quantities of Equipment to Be Purchased The County will be purchasing the following quantities of equipment from the Contractor: C.5.1 Dispatch Console Workstations The County will be purchasing a total of thirty-one dispatch console workstations, divided up among the following locations: C.5.1.1 Sixteen dispatch console workstations located at the Sheriff's Dispatch Center. C.5.1.1.1 C.5.2 May 17, 2012 An additional twelve operator positions shall be cabled to receive future dispatch console workstations. C.5.1.2 Nine dispatch console workstations located at the Adult Probation Dispatch Center. C.5.1.3 Two dispatch console workstations located at the Animal Care and Control Dispatch Center. C.5.1.4 One dispatch console workstation located at the Flood Control District AOC. C.5.1.5 Two dispatch console workstation located at the MCDOT Dispatch Center. C.5.1.6 One dispatch console workstation at the OET Wireless Systems Division office. Subscriber Radio Equipment The County expects to purchase approximately 3,500 units of Subscriber Radio Equipment over the life of this contract, beginning in the year 2013. Quantities are expected to be 1,000 units per year until the year 2016. Orders will be placed for a mixture of the various types of Subscriber Radio Equipment. The exact dates and quantities may vary. C.5.2.1 The County will be purchasing a sufficient number of new P25 Phase 2 (TDMA)-equipped trunked control stations to replace the existing control stations that are not P25 Phase 2 capable. C.5.2.2 The County will be purchasing a sufficient quantity of conventional control stations and base stations to replace existing control stations and base stations that are greater than seven years old (see Section D.22.6). C.5.2.3 The County will be purchasing a sufficient quantity of conventional control stations and base stations to fulfill the interoperability requirements of Section D.21.22. Document 2 - Specification & Response Document Page 28 of 399 Maricopa County, Arizona C.5.2.4 12030-RFP P25 Radio System Infrastructure Upgrade Additional purchases of subscriber radio equipment may be made by non-County agencies or others authorized to purchase from the Contract. C.5.3 Jail Emergency Consoles The County will be purchasing up to twenty Jail Emergency Consoles, two for each jail plus two spares. See Section D.21.21. C.5.4 Call Boxes The County will be purchasing fourteen Call Boxes to replace the existing fourteen Call Boxes. See Section D.21.23. C.5.5 Key Variable Loaders The County will be purchasing a quantity of three Key Variable Loaders. See Section D.21.18. C.5.6 Alarm and Diagnostic Subsystem User Workstations The County will be purchasing a total of five Alarm and Diagnostic Subsystem User Workstations, divided among the following locations: C.5.7 C.5.8 May 17, 2012 C.5.6.1 Four user workstations at the Durango Radio Shop C.5.6.2 One user workstation at the Backup Master Network Switch location. C.5.6.3 See Section D.24. System Administration Subsystem User Workstations The County will be purchasing a total of seven System Administration Subsystem User Workstations, divided among the following locations: C.5.7.1 Four user workstations at the Durango Radio Shop C.5.7.2 One user workstation at the Backup Master Network Switch location. C.5.7.3 One user workstation located at the Sheriff's Department. C.5.7.4 One user workstation located at Adult Probation. C.5.7.5 See Section D.25. Other Equipment Quantities of all other equipment will be determined by the Respondent/Contractor's design. Document 2 - Specification & Response Document Page 29 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.5 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.5 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Comply Standard Requirement Comply/ Section Exception C.5 C.5.1 C.5.1.1 C.5.1.1.1 C.5.1.2 C.5.1.3 C.5.1.4 C.5.1.5 C.5.1.6 C.5.2 C.5.2.1 C.5.2.2 C.5.2.3 C.5.2.4 C.5.3 C.5.4 C.5.5 C.5.6 C.5.6.1 C.5.6.2 C.5.6.3 C.5.7 C.5.7.1 C.5.7.2 C.5.7.3 C.5.7.4 C.5.7.5 C.5.8 {End Section C.5} May 17, 2012 Document 2 - Specification & Response Document Page 30 of 399 Maricopa County, Arizona C.6 12030-RFP P25 Radio System Infrastructure Upgrade Delivery of Materials, Site Construction and Site Improvements, Installation of Equipment The Contractor's responsibilities shall specifically include, but not be limited to: C.6.1 Preparation of environmental, biological and cultural studies and reports for all Project work as required by Federal, State and local laws, ordinances and codes. See Section D.6. C.6.2 Mitigation of impediments to Project work discovered through the environmental, biological and cultural studies and reports described above, in accordance with Federal, State and local laws, ordinances and codes. See Section D.6. C.6.3 Structural analysis of existing towers and other existing antenna support structures (including foundations) that are proposed for use as part of the Radio System to determine whether the structures are able to support additional antennas, cables and hardware. See Section D.9. C.6.4 Inspection of existing equipment spaces and other locations where equipment for the Radio System is proposed to be installed, to determine space requirements, floor loading weight constraints, building and fire code compliance, electrical, telecommunications, cabling, and heating, cooling and ventilation requirements. See Section D.17. C.6.5 Inspection of all proposed equipment locations for the presence of hazardous materials and the mitigation of any hazardous materials found, in accordance with Federal, State and local laws, ordinances and codes. C.6.6 Modification of existing towers and other existing antenna support structures, or construction of new towers and other antenna support structures, if required to provide an acceptable support structure for the Radio System antennas and/or to meet the radio coverage requirements described in this RFP. See Section D.14. C.6.7 Obtain any and all necessary environmental permits, construction permits and construction code inspections from the authorities having jurisdiction, at the Contractor's sole cost and expense. C.6.8 Modification of existing equipment spaces, or construction of new equipment spaces, in accordance with all applicable building codes, ordinances and regulations, the requirements of this RFP and modern industry best practices for such modification or construction, as required to provide acceptable, climate-controlled spaces for equipment and to meet other requirements described in this RFP. See Sections D.15, D.16 and D.17. C.6.9 All other work required to accomplish improvements to antenna sites and other equipment locations including but not limited to: clearing, grading, earthwork, construction or repair of access roads, camouflage of antennas and antenna support structures and landscaping. See Section D.7. May 17, 2012 Document 2 - Specification & Response Document Page 31 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade C.6.10 Provision, delivery and installation of electronic and ancillary equipment at antenna sites and other equipment locations. C.6.10.1 If necessary, Contractor shall provide secure storage within Maricopa County for all equipment prior to delivery to its final destination. C.6.11 Securing finished and unfinished Sites against unauthorized access, theft and vandalism, including but not limited to fencing, gates, barricades, electronic access control systems and electronic surveillance systems. C.6.11.1 The Contractor and its subcontractors shall comply with policies and procedures that have been or may be established by the County. C.6.12 Provision and installation of dispatch consoles and ancillary equipment, including software upgrades if required, as described in Section D.22 of this RFP. C.6.13 Modification of, or if necessary, replacement of control stations used by the User Agencies. See Section D.22.6. C.6.14 Provision of primary power, telephone service, and any other utilities necessary for the operation of electrically-powered equipment at Antenna Sites and other Sites. See Section D.7.4. C.6.15 Establishment of a safety program to include safety standards and procedures, safety inspections and provision of safety equipment at work sites for workers and visitors. The safety program shall comply with all Federal, State and local laws and best industry practices. See Section D.3. C.6.16 Establishment of a quality program to ensure that all materials and all work comply with all applicable laws, codes and ordinances, and meets or exceeds the requirements of this RFP and best industry practices. See Section D.2.1. C.6.17 Replacement of the Emergency Consoles used in each jail to alert jail personnel that an officer has pushed their EM button. See Section D.21.21. C.6.18 Replacement of Call boxes used by the public to contact Sheriff's Dispatch in areas where there is poor or no cell phone service. See Section D.21.23. C.6.19 The Contractor shall provide a sufficient number of staff and engage a sufficient number of subcontractors to ensure that all work is successfully completed in accordance with the approved Project Schedule. May 17, 2012 Document 2 - Specification & Response Document Page 32 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.6 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.6 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception C.6 C.6.1 C.6.2 C.6.3 C.6.4 C.6.5 C.6.6 C.6.7 C.6.8 C.6.9 C.6.10 C.6.10.1 C.6.11 C.6.11.1 C.6.12 C.6.13 C.6.14 C.6.15 C.6.16 C.6.17 C.6.18 C.6.19 {End Section C.6} May 17, 2012 Document 2 - Specification & Response Document Page 33 of 399 Maricopa County, Arizona C.7 12030-RFP P25 Radio System Infrastructure Upgrade Pre-Installation Testing (Staging or Factory Acceptance Testing) Prior to delivery to its final destination, the Contractor shall connect the Radio System equipment and test it as an integrated whole at the Contractor’s facility to ensure that it meets all published specifications and the requirements of this RFP. One or more representatives of the County shall witness Pre-Installation Testing. C.7.1 May 17, 2012 If necessary to meet the requirements for Commissioning, Migration and DeCommissioning (Section D.29), Pre-Installation Testing of a portion of the Radio System shall be permitted. Document 2 - Specification & Response Document Page 34 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.7 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.7 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Standard Standard Requirement Comply/ Section Exception C.7 C.7.1 {End Section C.7} May 17, 2012 Document 2 - Specification & Response Document Page 35 of 399 Maricopa County, Arizona C.8 12030-RFP P25 Radio System Infrastructure Upgrade Programming of Subscriber Radios The Contractor shall program the existing Subscriber Radios of the User Agencies to work with the new Radio System equipment. In addition: C.8.1 The Contractor shall assist the County in developing a new plan for programming of Subscriber Radios ("Fleet Map") based on the coverage, capacity and features available through the new Radio System infrastructure. C.8.2 The Contractor shall assist the County in developing programming templates for each individual User Agency for all types and models of Subscriber Radios used. C.8.3 The Contractor shall assume that Subscriber Radios will require programming multiple times. C.8.4 Programming of Subscriber Radios shall take place primarily at the end-user's work locations. May 17, 2012 Document 2 - Specification & Response Document Page 36 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.8 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.8 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Requirement Comply/ Section Exception C.8 C.8.1 C.8.2 C.8.3 C.8.4 {End Section C.8} May 17, 2012 Document 2 - Specification & Response Document Page 37 of 399 Maricopa County, Arizona C.9 12030-RFP P25 Radio System Infrastructure Upgrade Acceptance Testing The Contractor shall perform Acceptance Tests on the Radio System. The tests shall include but not be limited to: C.9.1 Testing of all components individually to verify that they meet manufacturer's published specifications and the requirements of this RFP. C.9.2 Testing of each sub-system (example: backhaul sub-system) to ensure that each subsystem meets manufacturer's published specifications and the requirements of this RFP (example: end-to-end Bit Error Rate test). C.9.3 Testing of the Radio System as an integrated whole to ensure that the Radio System meets manufacturer's published specifications and the requirements of this RFP. C.9.4 Verification of radio coverage provided by the completed Radio System. C.9.5 A Ninety-Day Reliability Test. C.9.6 Details of requirements for Acceptance Testing are described in Section D.27 of this RFP. May 17, 2012 Document 2 - Specification & Response Document Page 38 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.9 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.9 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception C.9 C.9.1 C.9.2 C.9.3 C.9.4 C.9.5 C.9.6 {End Section C.9} May 17, 2012 Document 2 - Specification & Response Document Page 39 of 399 Maricopa County, Arizona C.10 12030-RFP P25 Radio System Infrastructure Upgrade Archive Documents Archive Documents shall be provided to the County by the Contractor prior to Final Acceptance of the Project. Details of requirements for Archive Documents are described in Section D.30 of this RFP. May 17, 2012 Document 2 - Specification & Response Document Page 40 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.10 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.10 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception C.10 {End Section C.10} May 17, 2012 Document 2 - Specification & Response Document Page 41 of 399 Maricopa County, Arizona C.11 12030-RFP P25 Radio System Infrastructure Upgrade Training The Contractor shall train the personnel of the User Agencies in the proper operation of their mobile and portable radios as they have been modified to work with the new Radio System, and train system administration and maintenance personnel in the proper operation, care and maintenance of the Radio System. Details of requirements for Training are described in Section D.28 of this document. May 17, 2012 Document 2 - Specification & Response Document Page 42 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.11 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.11 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception C.11 {End Section C.11} May 17, 2012 Document 2 - Specification & Response Document Page 43 of 399 Maricopa County, Arizona C.12 12030-RFP P25 Radio System Infrastructure Upgrade Commissioning, Migration and Decommissioning The Contractor shall commission the new Radio System, migrate all mobile, portable and control station radio equipment onto it and put it in normal daily service. At the direction of the County, the Contractor shall decommission, remove and dispose of any legacy radio equipment that is to be removed. Details of requirements for Commissioning, Migration and Decommissioning are described in Section D.29 of this document. C.12.1 In the event that legacy equipment not being re-used in the new Radio System has any residual value, the Contractor shall remove and dispose of the legacy equipment and a credit shall be given to the County against the cost of the new Radio System. May 17, 2012 Document 2 - Specification & Response Document Page 44 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.12 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.12 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Standard Standard Requirement Comply/ Section Exception C.12 C.12.1 {End Section C.12} May 17, 2012 Document 2 - Specification & Response Document Page 45 of 399 Maricopa County, Arizona C.13 12030-RFP P25 Radio System Infrastructure Upgrade Final Acceptance The Radio System will be eligible for Final Acceptance: C.13.1 After all construction and installation work has been completed, including all Punch List items, and C.13.2 After all Acceptance Tests have been completed successfully, and C.13.3 After all Training has been completed successfully, and C.13.4 After all programming of mobile, portable and control station radio equipment has been completed successfully, and C.13.5 After the Radio System has been commissioned successfully and put into normal, everyday use, and C.13.6 After all Archive Documents have been delivered by the Contractor and approved by the County. May 17, 2012 Document 2 - Specification & Response Document Page 46 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.13 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.13 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception C.13 C.13.1 C.13.2 C.13.3 C.13.4 C.13.5 C.13.6 {End Section C.13} May 17, 2012 Document 2 - Specification & Response Document Page 47 of 399 Maricopa County, Arizona C.14 12030-RFP P25 Radio System Infrastructure Upgrade Warranties The Contractor shall warrant that all equipment, materials and work complies with the requirements of this RFP and is free of defects. See Section D.31 for details of Warranty requirements. May 17, 2012 Document 2 - Specification & Response Document Page 48 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.14 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.14 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception C.14 {End Section C.14} May 17, 2012 Document 2 - Specification & Response Document Page 49 of 399 Maricopa County, Arizona C.15 12030-RFP P25 Radio System Infrastructure Upgrade Optional Post-Warranty Maintenance and Repair Services After the expiration of all Warranties, the County may elect to hire the Contractor to maintain and repair selected portions of the Radio System or the entire Radio System. Details of requirements for Post-Warranty Maintenance and Repair Services are contained in Section D.32 of this document. May 17, 2012 Document 2 - Specification & Response Document Page 50 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.15 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.15 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception C.15 {End Section C.15} May 17, 2012 Document 2 - Specification & Response Document Page 51 of 399 Maricopa County, Arizona C.16 12030-RFP P25 Radio System Infrastructure Upgrade Time to Complete Project The Project shall be substantially complete within five years from date of Contractor's receipt of the County’s written Notice to Proceed. The Project shall be completed (Final Completion) and ready for final payment within 60 calendar days from the date of the Contractor's substantial completion determination. May 17, 2012 Document 2 - Specification & Response Document Page 52 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section C.16 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section C.16 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception C.16 {End Section C.16} May 17, 2012 Document 2 - Specification & Response Document Page 53 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SECTION D - TECHNICAL AND FUNCTIONAL SPECIFICATIONS D.1 Radio System Architecture and General Requirements D.1.1 General Requirements D.1.1.1 All components and equipment provided by the Contractor shall be suitable for the environment in which it shall be installed. For example, equipment installed at antenna sites shall be resistant to electromagnetic fields and high voltage transients caused by lightning and shall perform properly in a high RF environment. This requirement includes operating temperature and humidity, altitude, electromagnetic compatibility, primary power voltage, backup power voltage, frequency and phase. D.1.1.2 The Contractor shall make their best effort to provide components and equipment that continue to perform properly during failures of environmental control systems which may result in high or low temperatures, low or high humidity, and/or high levels of dust, dirt or air pollutants within the equipment space. D.1.1.2.1 D.1.2 May 17, 2012 Components and equipment shall be protected from damage due to failures of environmental control systems. D.1.1.3 All Radio System components and equipment shall be of current design and manufacture. Equipment not in current production or that is scheduled for discontinuance of production within seven (7) years of the date of Contract award is not acceptable. Note: This requirement does not apply to networking equipment such as computers, servers, routers and switches. D.1.1.4 All Radio System equipment and components shall be new and unused at the time of installation. D.1.1.5 Unless otherwise stated, the use of brand names in the body of this document is for convenience and to establish minimum acceptable specifications. Other manufacturers or models that meet equivalent specifications shall also be acceptable. Internet Protocol The Radio System shall utilize Ethernet and Internet Protocol ("IP") as its primary interconnection mechanism. D.1.2.1 The County desires to eliminate channelized DS-0. DS-1 and DS-3 circuits wherever possible. D.1.2.2 The Radio System shall be compliant with IETF RFC-1918 "Address Allocation for Private Internets" Document 2 - Specification & Response Document Page 54 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.1.3 Windows 7 General-purpose computers having a human interface shall use the Windows 7 operating system, or the most current operating system that has been approved by Maricopa County OET at the time of installation. D.1.4 General Requirements for Reliability and Redundancy D.1.4.1 All critical components shall utilize N+1 redundancy wherever possible May 17, 2012 D.1.4.2 To the extent possible, critical components shall be composed of modular, field replaceable units ("FRUs") for ease of maintenance. D.1.4.3 FRUs shall be hot-swappable to the greatest extent possible. D.1.4.4 Primary and backup redundant components shall have separate power circuits fed from different circuit breakers. Document 2 - Specification & Response Document Page 55 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.1 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.1 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Requirement Comply/ Section Exception D.1 D.1.1 D.1.1.1 D.1.1.2 D.1.1.2.1 D.1.1.3 D.1.1.4 D.1.1.5 D.1.2 D.1.2.1 D.1.2.2 D.1.3 D.1.4 D.1.4.1 D.1.4.2 D.1.4.3 D.1.4.4 {End Section D.1} May 17, 2012 Document 2 - Specification & Response Document Page 56 of 399 Maricopa County, Arizona D.2 12030-RFP P25 Radio System Infrastructure Upgrade Workmanship Requirements D.2.1 Quality Program The Contractor shall institute a Quality Program to ensure that all work complies with the requirements of this RFP and the best design, engineering, construction and installation practices. The program shall include quality familiarization and training, quality inspections, quality reporting and quality monitoring. D.2.1.1 Quality Training and Familiarization D.2.1.1.1 The Contractor's personnel and the personnel of all subcontractors shall have been adequately trained or shall receive, prior to start of work, adequate training regarding the work they will be performing. For example, workers that are installing a ground system shall have been trained in the proper standards and methods for performing such work. D.2.1.1.2 D.2.1.2 May 17, 2012 Immediately prior to the start of work, all work crews will receive a Quality Familiarization briefing to describe the level of quality that is expected, and to highlight the items that the County will look for in its Quality Inspections. Quality Inspections The County shall inspect all work performed by the Contractor for compliance to the requirements of this RFP, compliance with best design, engineering and installation practices, conformance to all applicable building codes and conformance to all applicable laws and regulations. Following each inspection the County shall provide to the Contractor a list of any defects noted during the inspection ("Punch List"). The Contractor shall correct all defects listed on the Punch List within ten (10) business days. Upon correction of the Punch List items, the items on the Punch List shall be re-inspected by the County. If Punch List items have not been corrected to the satisfaction of the County, a new Punch List shall be provided by the County to the Contractor. D.2.1.2.1 The Contractor shall have pre-inspected all work and repaired defects prior to notifying the County that the work is ready for inspection. D.2.1.2.2 The County reserves the right to designate a third party to perform inspections and issue Punch Lists to the Contractor. D.2.1.2.3 Work shall not be accepted by the County until all Punch List items have been corrected. Document 2 - Specification & Response Document Page 57 of 399 Maricopa County, Arizona D.2.1.3 12030-RFP P25 Radio System Infrastructure Upgrade Quality Reporting and Quality Monitoring The Contractor shall institute a process for reporting the level of quality achieved, and for monitoring quality trends so that remedial action may be taken on a timely basis if necessary. D.2.1.3.1 The Contractor shall prepare monthly quality reports to the County describing the level of quality being obtained, noteworthy quality trends and issues, any remedial action taken and the results of such action(s). D.2.2 Grounding, Lightning and Transient Suppression The Contractor shall comply with the Standards for Grounding and Lightning and Transient Suppression which are contained in Appendix 5. D.2.3 Cabling D.2.3.1 May 17, 2012 Electrical work (including low-voltage and signal cabling) shall comply with the National Electrical Code, Building Codes, and all applicable local laws, regulations, codes and standards. D.2.3.2 Low voltage, high current power sources (example: -48 Volt DC power system) shall have all bus bars and distribution points protected against accidental contact with tools, jewelry or other conductive objects. Such circuits shall also be protected with appropriately rated circuit breakers. D.2.3.3 Cables shall be installed in such a manner as to facilitate ease of removal and shall not hinder the removal of any existing cabling. D.2.3.4 All cables shall be routed and secured in a neat, professional manner. D.2.3.5 Use of electrical extension cords shall not be permitted for permanent equipment installation but may be used temporarily during the installation work. D.2.3.5.1 Extension cords shall be "OSHA Orange" in color. D.2.3.5.2 Extension cords shall be run so as not to present a hazard. D.2.3.6 Each run of cable shall be one continuous piece without a splice or midspan connectors. D.2.3.7 Cables shall be appropriately separated to prevent inductive or capacitive coupling and inter-cable interference. The Contractor shall be responsible for eliminating any inter-cable interference. D.2.3.8 Cables, connectors and grounding kits installed outdoors shall be properly weatherproofed using the cable and connector manufacturer's recommended products and procedures. Document 2 - Specification & Response Document Page 58 of 399 Maricopa County, Arizona D.2.3.9 12030-RFP P25 Radio System Infrastructure Upgrade Points where cables or waveguides enter an equipment space from outdoors shall be sealed and weatherproofed. D.2.3.9.1 D.2.4 May 17, 2012 Just before the point of entry, all cables entering shall have a drip loop to prevent water entry into the equipment space. D.2.3.10 Coaxial cables, waveguides and other cables entering a building from outdoors shall have lightning suppression devices installed and be properly grounded in compliance with the requirements contained in Appendix 5. D.2.3.11 Coaxial cables and waveguides installed outdoors shall be supported at the manufacturer's recommended intervals based on the cable type and a wind speed of 100 miles per hour. D.2.3.12 Coaxial cable and waveguide supports used shall be those recommended by the manufacturer for that cable type under the specified conditions. D.2.3.13 Cables shall be installed in a manner that allows for easy maintenance and servicing. D.2.3.14 Special Consideration for Data Center Environments Locations where the Master Network Switch and the Backup Master Network Switch are to be installed shall be considered "Data Center Environments." The Maricopa County Office of Enterprise Technology ("OET") has specific cabling and grounding standards for such environments (document A-1201-S-02). The standards document is contained in Appendix 9 of this document. The Contractor shall comply with the A-1201-S-02 standard when working in Data Center Environments. NOTE: The words "should" and "must" shall be construed to mean "shall." Installation of Equipment D.2.4.1 Installation work shall be performed in a neat and professional manner and shall be consistent with OSHA requirements and the best design, engineering and installation practices. D.2.4.2 Any damage done by the Contractor or its Subcontractors to County property or the property of others as a result of Project work shall be repaired at no cost to the County. D.2.4.3 At indoor locations where there is a clean, secure, environmentallyconditioned room expressly for the installation of Radio System equipment and/or other telecommunications equipment, the Radio System equipment may be installed in open 19 inch EIA racks. Document 2 - Specification & Response Document Page 59 of 399 Maricopa County, Arizona D.2.4.4 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.2.4.3.1 In such cases, the Contractor shall verify that the existing AC power and environmental conditioning systems are sufficient for the Radio System equipment and any additional existing or planned telecommunications equipment. D.2.4.3.2 If any are found to be insufficient, the Contractor shall upgrade them as necessary. At indoor locations that are not secure or not environmentally conditioned (such as an apparatus bay of a fire station), the Radio System equipment shall be installed in locked, vandalism and tamperresistant, dust, dirt and moisture-proof, environmentally conditioned cabinets of all stainless steel exterior construction. D.2.4.4.1 The cabinets shall be designed for the mounting of electronic equipment in 19 inch EIA rack panels. D.2.4.4.2 Each cabinet shall have removable front and rear doors, with a hinge assembly designed for easy door removal and replacement. D.2.4.4.3 Cabinets shall be Hoffman “ProLine” cabinets or approved equal. D.2.4.4.4 The cabinets shall be securely bolted to the floor of the installation location. D.2.4.4.5 AC power and telecommunications circuits shall be run to and from the cabinets in rigid metallic conduit. D.2.4.4.6 Each cabinet shall be provided with either filtered fan cooling or air conditioning, as required by the equipment and depending upon conditions at the installation location. D.2.4.5 Equipment, parts and components shall be installed in a manner that allows for easy maintenance and servicing. D.2.4.6 Accessibility to installed equipment shall be to OSHA standards D.2.4.7 Equipment, parts and components shall be installed securely in a manner that prevents movement in the event of an earthquake or inadvertent contact by persons or objects. D.2.4.8 Equipment, parts and components shall be rack-mounted. D.2.4.9 Equipment shall be installed to meet seismic building code requirements. Document 2 - Specification & Response Document Page 60 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.2 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.2 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Standard Requirement Comply/ Section Exception D.2 D.2.1 D.2.1.1 D.2.1.1.1 D.2.1.1.2 D.2.1.2 D.2.1.2.1 D.2.1.2.2 D.2.1.2.3 D.2.1.3 D.2.1.3.1 D.2.2 D.2.3 D.2.3.1 D.2.3.2 D.2.3.3 D.2.3.4 D.2.3.5 D.2.3.5.1 D.2.3.5.2 D.2.3.6 D.2.3.7 D.2.3.8 D.2.3.9 D.2.3.9.1 D.2.3.10 D.2.3.11 D.2.3.12 D.2.3.13 D.2.3.14 D.2.4 D.2.4.1 May 17, 2012 Document 2 - Specification & Response Document Page 61 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.2 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.2.4.2 D.2.4.3 D.2.4.3.1 D.2.4.3.2 D.2.4.4 D.2.4.4.1 D.2.4.4.2 D.2.4.4.3 D.2.4.4.4 D.2.4.4.5 D.2.4.4.6 D.2.4.5 D.2.4.6 D.2.4.7 D.2.4.8 D.2.4.9 {End Section D.2} May 17, 2012 Document 2 - Specification & Response Document Page 62 of 399 Maricopa County, Arizona D.3 12030-RFP P25 Radio System Infrastructure Upgrade Safety Program The Contractor shall institute a Safety Program to ensure that the requirements of all applicable laws, regulations and codes, particularly Federal and State OSHA Regulations, are met. The program shall include safety training and briefings, safety inspections, safety reporting and safety monitoring. D.3.1 Safety Studies, Training and Awareness D.3.1.1 Where applicable, the Contractor shall perform engineering and other studies to determine the existence of hazardous materials and other safety hazards at work sites (example: Radio Frequency Radiation (RFR) studies to determine compliance with FCC O.E.T. Bulletin No. 65 for occupational exposure). D.3.1.2 The Contractor's personnel and the personnel of all subcontractors shall receive adequate training regarding the work they will be performing. Such training shall include safety standards and safe methods for performing the work. D.3.1.3 All work crews shall receive regular Safety Briefings to maintain their awareness of safety issues and their familiarity with safe work practices. D.3.1.4 The Contractor shall post safety warning and hazard notification signs as required by site conditions. D.3.1.5 Areas containing hazards shall be fenced or barricaded to prevent unnecessary entry. D.3.2 Safety Equipment The Contractor shall provide appropriate safety equipment for its personnel and the personnel of subcontractors. D.3.3 Safety Inspections The County shall periodically conduct Safety Inspections at work sites. The Contractor will be immediately notified of any safety violations and shall remedy them as required by law. D.3.4 Safety Reporting and Safety Monitoring The Contractor shall institute a process for reporting the level of safety achieved, and for monitoring safety trends so that remedial action may be taken on a timely basis if necessary. D.3.4.1 D.3.5 May 17, 2012 The Contractor shall prepare monthly safety reports to the County describing the level of safety being obtained, safety trends and issues, any remedial action taken and the results of such action(s). Other Elements The Safety program shall include all other elements that may be required by law or regulation. Document 2 - Specification & Response Document Page 63 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.3 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.3 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.3 D.3.1 D.3.1.1 D.3.1.2 D.3.1.3 D.3.1.4 D.3.1.5 D.3.2 D.3.3 D.3.4 D.3.4.1 D.3.5 {End Section D.3} May 17, 2012 Document 2 - Specification & Response Document Page 64 of 399 Maricopa County, Arizona D.4 12030-RFP P25 Radio System Infrastructure Upgrade Selection of Antenna Sites The Contractor/Respondent shall propose the use of antenna sites as required to fulfill the coverage requirements stated in Section D.20. When selecting sites to be proposed, the Contractor/Respondent shall select sites in the following order of preference, from most preferred to least preferred: D.4.1 Existing antenna sites already in use by the County. A list of existing County antenna sites is provided in Appendix 2. D.4.1.1 With the exception of the Humboldt, Chandler, Scottsdale Civic Center, Mt. Gillen and Towers sites, the existing antenna sites are County-owned, and the structure heights may be increased by a reasonable amount if necessary. Increases to the heights of non-County owned structures may be possible but must be negotiated with the site owners. D.4.1.2 The Emergency Management site is adjacent to a heliport and the ability to increase its height significantly may be limited. D.4.1.3 The Contractor shall not be required to use any existing Site in its design. D.4.2 Existing antenna sites owned or operated by other governmental entities are potential sites for the County's use through the negotiation and execution of an Intergovernmental Agreement ("IGA"). Also included are sites owned or operated by utilities or quasi-governmental entities (example: Salt River Project) that are potential sites for the County's use through negotiation and execution of use agreements. D.4.3 One of the three following options, to be selected based upon the least cost to Maricopa County over the twenty-year expected life of the Radio System: May 17, 2012 D.4.3.1 A new site constructed on existing County property. A map of County property that may be suitable as an antenna site is provided in Appendix 13. A shape file in Arc View format is also included in the Zip file that may be downloaded from the Maricopa County Office of Procurement Services web site, https://www.bidsync.com/. See Appendix 4. D.4.3.2 A new site constructed on Federal land that may be leased at a low cost (example: Bureau of Land Management or U.S. Forest Service) or other property that may be leased or purchased at a low cost. D.4.3.3 An existing leased commercial antenna site (example: sites owned by American Tower or Crown Castle) Document 2 - Specification & Response Document Page 65 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.4.4 The Contractor/Respondent shall be aware that some Federal, State, County, municipal and private property is designated as wilderness or has other significant environmental, cultural and site development issues. These issues and the associated project risks shall be taken into account by the Contractor/Respondent in its evaluation of a particular piece of property as a potential antenna site. As this Radio System is being specified as a turnkey project, the Contractor shall be responsible for mitigation of environmental, biological and cultural issues and provision of legal access to each site and electrical power at each site. D.4.5 The County will accept a small number of new sites that utilize electrical photovoltaic ("solar") power or other alternatives to commercial AC electrical power. Site power requirements are described in detail in Section D.10 of this RFP. May 17, 2012 Document 2 - Specification & Response Document Page 66 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.4 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.4 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.4 D.4.1 D.4.1.1 D.4.1.2 D.4.1.3 D.4.2 D.4.3 D.4.3.1 D.4.3.2 D.4.3.3 D.4.4 D.4.5 {End Section D.4} May 17, 2012 Document 2 - Specification & Response Document Page 67 of 399 Maricopa County, Arizona D.5 12030-RFP P25 Radio System Infrastructure Upgrade Site Acquisition Assistance The Contractor shall assist the County in the acquisition of real property, acquisition of easements, acquisition of ingress/egress, acquisition of leases, variances to zoning and acquisition of all other agreements necessary to construct or modify Antenna Sites or other Sites that are to be a part of the Radio System. D.5.1 The Contractor shall provide the following information for each Antenna Site proposed to be a part of the Radio System: D.5.1.1 Longitude and Latitude coordinates; D.5.1.2 Street address and nearest cross-street; D.5.1.3 Assessor's Parcel Number (APN); D.5.1.4 Name and contact information of property owner of record; D.5.1.5 Contact name, address, e-mail address and telephone number of property manager if other than the owner of record; D.5.1.6 Zoning of parcel and jurisdiction; D.5.1.7 Name of electrical service provider and number of nearest electrical pole, or, if underground, nearest address with commercial electric power, or, if it is not practical to bring commercial electric power to the site, the alternate power source being proposed; D.5.1.8 Easements that may be required for site access and provision of utility services; D.5.1.9 A constructability assessment describing in detail the work required to make the site suitable for use in the Radio System; and, D.5.1.10 APN's and name and contact information of owners of record of all adjacent properties. D.5.2 All information required by Section D.5.1 shall also be provided for a minimum of two alternative Antenna Sites that will be suitable as a replacement in the event the proposed property cannot be acquired. D.5.3 For all Antenna Sites and ingress/egress routes, provide recordable surveys and legal descriptions (prepared by a land surveyor licensed in the State of Arizona) for inclusion as Appendices in lease or purchase agreements, easements, construction drawings and other documents. The Contractor shall determine if legal access to the site exists and the Contractor shall document such legal access. If no legal access to the site exists, the Contractor shall determine what legal access to the site is necessary and the Contractor shall document that access in accordance with RFP requirements. In the case of public lands, such as May 17, 2012 Document 2 - Specification & Response Document Page 68 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade BLM and USFS, it is not necessary to survey existing mapped and named roads. A description such as “Forest Road 201” is sufficient. It is not necessary to survey roads owned or maintained by a site tenants’ association of which the County is a member or where a legal easement, to the benefit of the County, already exists. Surveys will be necessary when a proposed access road crosses private property or when a new road is proposed on public lands. D.5.4 D.5.5 May 17, 2012 The Contractor shall assist the County in preparing requests for zoning variances and in communicating with property owners, homeowners associations and other concerned parties, specifically including, but not limited to the following services: D.5.4.1 Creating and providing Zoning Drawings ("ZDs") D.5.4.2 Preparing engineering data and other information that may be required as justification of the need for an Antenna Site in a particular location D.5.4.3 Preparing Radio Frequency Radiation (RFR) studies to determine compliance with FCC guidelines (FCC O.E.T. Bulletin No. 65) for both occupational and uncontrolled exposure D.5.4.4 Preparing presentations, handouts and other informational materials In the event that one or more Antenna Sites proposed by the Contractor cannot be acquired by the County for any reason, the Contractor shall propose alternate sites that meet the coverage requirements and shall modify its Radio System design accordingly at no additional cost to the County. Document 2 - Specification & Response Document Page 69 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.5 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.5 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.5 D.5.1 D.5.1.1 D.5.1.2 D.5.1.3 D.5.1.4 D.5.1.5 D.5.1.6 D.5.1.7 D.5.1.8 D.5.1.9 D.5.1.10 D.5.2 D.5.3 D.5.4 D.5.4.1 D.5.4.2 D.5.4.3 D.5.4.4 D.5.5 {End Section D.5} May 17, 2012 Document 2 - Specification & Response Document Page 70 of 399 Maricopa County, Arizona D.6 12030-RFP P25 Radio System Infrastructure Upgrade Environmental, Biological, Cultural D.6.1 The Contractor shall prepare Environmental Impact Reports and other Environmental, Biological and Cultural studies as required for NEPA and ADEQ compliance. Any additional mitigation costs discovered during the post-sale engineering investigations will be the responsibility of the Contractor. D.6.2 The Contractor shall take whatever steps necessary to mitigate environmental, biological and cultural issues that are identified by the Environmental Biological and Cultural Studies. D.6.3 The Contractor shall obtain all environmental permits required for site construction and equipment installation, including, but not limited to: May 17, 2012 D.6.3.1 Dust Control Permit (Maricopa County Air Quality Department) D.6.3.2 Storm Water Permit (Maricopa County Department of Environmental Services) D.6.3.3 Any other required environmental permit. Document 2 - Specification & Response Document Page 71 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.6 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D. 6 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.6 D.6.1 D.6.2 D.6.3 D.6.3.1 D.6.3.2 D.6.3.3 {End Section D.6} May 17, 2012 Document 2 - Specification & Response Document Page 72 of 399 Maricopa County, Arizona D.7 12030-RFP P25 Radio System Infrastructure Upgrade Site Preparation The Contractor shall perform all site preparation work, which shall include but not be limited to: D.7.1 Temporary Access Roads During Project Work The Contractor shall repair and upgrade existing access roads and create new access roads, including bridges, grade crossings, water crossings and drainage, for access for construction equipment and materials. The Contractor shall maintain the access road in usable condition for the duration of work at the site. D.7.2 Permanent Access Roads for Maintenance Access At the conclusion of all Project work at a Site, the Contractor shall repair and upgrade existing access roads or create new access roads, including bridges, grade crossings, water crossings and drainage, for permanent maintenance access. MCDOT shall approve all plans and specifications for access roads. D.7.2.1 D.7.3 Helicopter Access Sites The County will consider a small number of site locations where it is impractical or prohibitively expensive to construct an access road and access by helicopter is the only solution. D.7.3.1 D.7.4 May 17, 2012 Upon conclusion of Project work at the Site and the completion of the permanent access road, the Contractor's responsibility for maintenance of the road shall terminate. Due to the high cost of construction and maintenance at helicopter access sites, the Respondent/Contractor shall propose them sparingly. Utilities The Contractor shall bring all necessary utilities (particularly commercial AC power) to each site for temporary use during site construction and for the permanent operation of the site. If the necessary utilities already exist, the Contractor shall determine whether the capacity of the existing services are sufficient and upgrade them if necessary. The Contractor will be viewed as the County’s agent in the case of dealing with utility providers. The Contractor shall negotiate with the provider, file all engineering and other documents with the utility and prepare application documents for signature by the County. All documents filed by the Contractor with the utility shall be approved by the County prior to presentation to the utility. The County will make the payment(s) to the utility for application fees and the cost of extending the utility service to the subject site. D.7.4.1 For sites where it is impractical or prohibitively expensive to provide commercial AC power, the County will permit the use of alternative power sources. D.7.4.2 Due to the high cost of construction and maintenance of alternative power sources, the Respondent/Contractor shall propose them sparingly. Document 2 - Specification & Response Document Page 73 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.7.5 Grading and Earthwork The Contractor shall perform any grading or other earthwork necessary to prepare sites for construction and installation activities. The Contractor shall construct retaining walls if necessary. D.7.6 Basic Site Requirements Sites shall include: D.7.6.1 Antenna support structure (if applicable) D.7.6.2 Equipment shelter or other suitable equipment space D.7.6.3 Primary and backup electrical power sources D.7.6.4 Cable support system D.7.6.4.1 Transmission line bridge/ice shield between equipment shelter and antenna support structure if outdoors; D.7.6.4.2 D.7.6.5 Fire Protection System Equipment spaces shall be equipped with an automatic fire protection system consisting of both fire alarm and fire suppression subsystems. See Section D.17.12. D.7.6.6 Physical Security See Section D.18 for detailed specifications regarding Physical Security. D.7.6.7 D.7.6.8 D.7.6.6.1 Fencing D.7.6.6.2 Locking gates and doors D.7.6.6.3 Access road gate (selected sites; at the direction of the County only) Electronic Security See Section D.26 for detailed specifications regarding Electronic Security D.7.6.7.1 Intrusion alarm (door sensor and/or motion detector) D.7.6.7.2 Access control system D.7.6.7.3 Video surveillance system Accessibility for Equipment and Personnel D.7.6.8.1 Ramps and other accommodations shall be provided wherever necessary for wheelchair access as applicable. D.7.6.8.2 May 17, 2012 Overhead cable ladders and conduit if indoors. Accessibility to installed equipment shall comply with OSHA requirements. Document 2 - Specification & Response Document Page 74 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.7 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.7 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Standard Standard Requirement Comply/ Section Exception D.7 D.7.1 D.7.2 D.7.2.1 D.7.3 D.7.3.1 D.7.4 D.7.4.1 D.7.4.2 D.7.5 D.7.6 D.7.6.1 D.7.6.2 D.7.6.3 D.7.6.4 D.7.6.4.1 D.7.6.4.2 D.7.6.5 D.7.6.6 D.7.6.6.1 D.7.6.6.2 D.7.6.6.3 D.7.6.7 D.7.6.7.1 D.7.6.7.2 D.7.6.7.3 D.7.6.8 D.7.6.8.1 D.7.6.8.2 {End Section D.7} May 17, 2012 Document 2 - Specification & Response Document Page 75 of 399 Maricopa County, Arizona D.8 12030-RFP P25 Radio System Infrastructure Upgrade Optional Low Environmental Impact Antenna Sites Much of Maricopa County is rural, and there are many environmentally-sensitive areas. In a small number of those areas, the County may optionally elect to construct sites that have a lower environmental impact than a full site with a tower, equipment shelter and ancillary equipment. There shall be two classifications: a Mini-Site and a Micro-Site. D.8.1 D.8.2 May 17, 2012 Mini-Site Mini-Sites shall have: D.8.1.1 Small physical footprint D.8.1.2 40 foot tower or monopole D.8.1.3 Solar power with battery backup D.8.1.4 Low power consumption D.8.1.5 Environmentally conditioned equipment spaces D.8.1.6 Fully trunked repeater operation D.8.1.7 Microwave backhaul D.8.1.8 Complete suite of alarm and diagnostic reporting D.8.1.9 Capability to withstand the extremes of weather common to Maricopa County, including temperature, rain, wind, dust and snow while remaining fully functional D.8.1.10 Grounding of tower, solar panels, electronic equipment and equipment space utilizing a minimum of two buried chemical ground rods D.8.1.11 Site security fencing D.8.1.12 Lower cost to construct than a full tower and shelter D.8.1.13 Unless otherwise stated, all other applicable Site specifications stated in this RFP shall apply. Micro-Site Micro-Sites shall have: D.8.2.1 Smallest possible physical footprint D.8.2.2 20 foot tower or monopole D.8.2.3 Solar power with battery backup D.8.2.4 Lowest possible power consumption D.8.2.5 Conventional P25 700 MHz or 800 MHz repeater connected to a mobile or control station so that transmissions on the conventional channel are re-transmitted to a trunked talkgroup, and vice-versa, much like a vehicular repeater. Document 2 - Specification & Response Document Page 76 of 399 Maricopa County, Arizona D.8.3 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.8.2.6 Capability to withstand the extremes of weather common to Maricopa County, including temperature, rain, wind, dust and snow while remaining fully functional D.8.2.7 Limited alarm and diagnostic reporting, including but not limited to low battery alarm D.8.2.8 Grounding of tower, solar panels, electronic equipment and equipment space utilizing a minimum of one buried chemical ground rod D.8.2.9 Site security fencing D.8.2.10 Lower cost to construct than a Mini-Site D.8.2.11 Unless otherwise stated, all other applicable antenna site specifications stated in this RFP shall apply. Other Configurations Additional low environmental impact site configurations may be proposed at the discretion of the Contractor. Document 2 - Specification & Response Document Page 77 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.8 Response Form Respondent: RFP Section: 12030-RFP, Document 2, Section D.8 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. Standard/ Requirement Comply/ 2) Respondents shall indicate the feature being provided is a Custom/ Section Exception Standard feature, requires Customization, or is being 3rd Party provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. D.8 D.8.1 D.8.1.1 D.8.1.2 D.8.1.3 D.8.1.4 D.8.1.5 D.8.1.6 D.8.1.7 D.8.1.8 D.8.1.9 D.8.1.10 D.8.1.11 D.8.1.12 D.8.1.13 D.8.2 D.8.2.1 D.8.2.2 D.8.2.3 D.8.2.4 D.8.2.5 D.8.2.6 D.8.2.7 D.8.2.8 D.8.2.9 D.8.2.10 D.8.2.11 D.8.3 (Choose One) (Choose One) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Reason for exception and alternative to specification requirement. {End Section D.8} May 17, 2012 Document 2 - Specification & Response Document Page 78 of 399 Maricopa County, Arizona D.9 12030-RFP P25 Radio System Infrastructure Upgrade Site Engineering, Plans & Construction Drawings The Contractor shall provide the following: D.9.1 Geotechnical Report The Contractor shall provide a geotechnical report based on soil borings and other technical investigations for each site where tower or equipment shelter construction will be performed. The report shall include: D.9.1.1 An analysis of soil and seismic conditions in sufficient detail that a competent engineer may produce tower, equipment shelter and other structural drawings and engineering documents; D.9.1.2 An analysis of soil corrosiveness and recommendations to prevent damage to and premature failure of buried foundations and buried electrical conductors. The recommendations shall include: D.9.1.2.1 D.9.2 D.9.3 May 17, 2012 A recommended concrete mix design specifying anticorrosive additives. Structural Analysis All existing antenna support structures proposed to be used as part of the Radio System shall undergo a detailed structural analysis to determine the structure's ability to support existing loads and new loads that will be applied due to Radio System implementation. D.9.2.1 Structural analyses, including analyses of foundations and attachments to building structures, shall comply with the requirements of a "rigorous analysis" as defined in TIA-222-G. D.9.2.2 If strengthening of the existing structure or its foundation is required, the structural analysis shall describe in detail the materials, methods and procedures required to strengthen the structure. Plans and Drawings For every Site, the Contractor shall provide a complete set of plans and drawings, including, but not limited to: D.9.3.1 A site survey performed by a surveyor licensed in the State of Arizona D.9.3.2 A metes and bounds description of property or leased area D.9.3.3 A plot plan D.9.3.4 Plan(s) for temporary and finished site earthwork and grading D.9.3.5 North, south, east and west elevation drawings D.9.3.6 Structural, mechanical, electrical and fire protection system drawings for equipment shelter(s) and equipment space(s) Document 2 - Specification & Response Document Page 79 of 399 Maricopa County, Arizona D.9.3.7 12030-RFP P25 Radio System Infrastructure Upgrade Tower (or other antenna support structure) structural and foundation design drawings. D.9.3.7.1 D.9.4 May 17, 2012 The engineering calculations that resulted in the design shall be provided for review by the County. D.9.3.8 Foundation design and equipment installation drawings for ancillary equipment, including but not limited to generators and fuel tanks D.9.3.9 Interior and exterior grounding plans D.9.3.10 Construction and installation specifications, including specifications for soil compaction, backfilling and grading. D.9.3.11 A dust control plan D.9.3.12 A storm water pollution prevention plan ("SWPPP") D.9.3.13 In instances where existing equipment spaces are being remodeled, the Contractor shall provide the applicable subset of the above plans and drawings. D.9.3.14 Surveys, plans and drawings shall be printed in ANSI E size in order to provide a sufficient level of detail. D.9.3.14.1 The County shall be provided with AutoCAD files of all drawings per FMD standards. D.9.3.14.2 Copies of surveys, plans and drawings may be printed in smaller sizes if desired, but copies submitted for permit must be full size. D.9.3.15 All designs, plans and drawings shall be signed and sealed by a Professional Engineer currently licensed in the State of Arizona. D.9.3.16 All surveys, designs, plans and drawings shall receive approval from the County prior to submission to permitting authorities and/or the start of work. Ownership of Plans, Drawings, Documents, and Specifications All drawings and documents submitted by the Contractor to the County shall become the property of the County. Proprietary information provided by the Contractor shall be clearly labeled. Document 2 - Specification & Response Document Page 80 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.9 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.9 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.9 D.9.1 D.9.1.1 D.9.1.2 D.9.1.2.1 D.9.2 D.9.2.1 D.9.2.2 D.9.3 D.9.3.1 D.9.3.2 D.9.3.3 D.9.3.4 D.9.3.5 D.9.3.6 D.9.3.7 D.9.3.7.1 D.9.3.8 D.9.3.9 D.9.3.10 D.9.3.11 D.9.3.12 D.9.3.13 D.9.3.14 D.9.3.14.1 D.9.3.14.2 D.9.3.15 D.9.3.16 D.9.4 {End Section D.9} May 17, 2012 Document 2 - Specification & Response Document Page 81 of 399 Maricopa County, Arizona D.10 12030-RFP P25 Radio System Infrastructure Upgrade Site Primary Power Specifications D.10.1 Commercial AC Power The Contractor shall be responsible for all commercial AC power installation. If necessary, the County will assist the Contractor in arranging for commercial power installation to the meter. The Contractor shall be responsible for the provision of electrical utility service to the site as described in section D.7.4 of this specification. D.10.1.1 Power feeds to shelters may be buried or aerial as required by local zoning, regulations or community standards, or as directed by the County. D.10.1.2 If a main cutoff switch is required outside of the shelter, this switch shall be padlocked with a lock keyed to the County’s specification. D.10.1.3 Power installation shall comply with the NEC and all applicable building codes. D.10.1.4 At a minimum, electrical systems shall be 200 Amp, 120 / 240-volt, 60 Hz, single phase, unless a greater capacity is needed. D.10.2 Photovoltaic ("Solar") Power Systems For sites that will be solar-powered, the Contractor shall provide the following: D.10.2.1 Solar Panel Array D.10.2.2 NEMA-4 environmentally sealed equipment enclosure(s), where applicable D.10.2.3 System Controller D.10.2.4 48 Volt (nominal) Battery Bank D.10.2.5 48 Volt (nominal) Battery Charger. See applicable portions of Section D.11 of this document. D.10.2.5.1 May 17, 2012 Battery charger shall incorporate a protection circuit to prevent overcharging of batteries. D.10.2.6 DC charge Controller D.10.2.7 Low-voltage disconnect D.10.2.8 DC Distribution Panel that complies with the requirements of Section D.11.7 of this document. D.10.2.9 DC Surge Protection D.10.2.10 DC to DC converter(s), if applicable, that complies with the requirements of Section D.11.5 of this document. D.10.2.11 DC to AC Inverter (s), if applicable, that complies with the requirements of Section D.11.6 of this document. Document 2 - Specification & Response Document Page 82 of 399 Maricopa County, Arizona D.10.2.12 AC Distribution Panel, if applicable D.10.2.13 AC Surge Protection, if applicable D.10.2.14 Required Environmental Specifications for Solar Power Systems D.10.2.14.1 Temperature Range: -30°C to 50˚C D.10.2.15 D.10.2.16 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.10.2.14.2 Humidity: 100% condensing D.10.2.14.3 Altitude: All equipment shall be rated at full specifications at the altitude at which it will be installed. D.10.2.14.4 Wind Survivability: 90 mph minimum D.10.2.14.5 Seismic Zone 1 Required Electrical Specifications for Solar Power Systems D.10.2.15.1 Output Voltage: 48 VDC (nominal) D.10.2.15.2 Current Capacity: Shall be equipped to deliver a minimum of 125% of the maximum current required to operate the site at full capacity at 100% duty cycle. D.10.2.15.3 Battery Runtime: minimum of eight days of overcast daytime weather conditions D.10.2.15.4 Configuration: Single bank configuration D.10.2.15.5 Battery Type: Sealed Lead Acid (Maintenance Free). Vendors may propose alternative battery chemistries that are superior to the one specified, if desired. D.10.2.15.6 Battery Capacity: As required to meet the foregoing electrical specifications D.10.2.15.7 Batteries shall be warranted by the manufacturer for a minimum of three years. D.10.2.15.8 Complete System shall meet NEC requirements Additional Requirements for Solar Power Systems D.10.2.16.1 Local Metering and Diagnostics: Solar power systems shall be equipped with a local metering and diagnostic system that includes but is not limited to monitoring of: D.10.2.16.1.1 Solar panel voltage and current D.10.2.16.1.2 Battery charger output voltage and current D.10.2.16.1.3 Battery charge and condition D.10.2.16.1.4 Major and minor alarms Document 2 - Specification & Response Document Page 83 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.10.2.16.2 Remote Metering and Diagnostics: All the metering and diagnostics capability listed above shall be available remotely through the Diagnostic and Monitoring System specified in Section D.24 of this document. Section D.10 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.10 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.10 D.10.1 D.10.1.1 D.10.1.2 D.10.1.3 D.10.1.4 D.10.2 D.10.2.1 D.10.2.2 D.10.2.3 D.10.2.4 D.10.2.5 D.10.2.5.1 D.10.2.6 D.10.2.7 D.10.2.8 D.10.2.9 D.10.2.10 D.10.2.11 D.10.2.12 D.10.2.13 D.10.2.14 D.10.2.14.1 D.10.2.14.2 D.10.2.14.3 D.10.2.14.4 D.10.2.14.5 May 17, 2012 Document 2 - Specification & Response Document Page 84 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.10 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.10.2.15 D.10.2.15.1 D.10.2.15.2 D.10.2.15.3 D.10.2.15.4 D.10.2.15.5 D.10.2.15.6 D.10.2.15.7 D.10.2.15.8 D.10.2.16 D.10.2.16.1 D.10.2.16.1.1 D.10.2.16.1.2 D.10.2.16.1.3 D.10.2.16.1.4 D.10.2.16.2 {End Section D.10} May 17, 2012 Document 2 - Specification & Response Document Page 85 of 399 Maricopa County, Arizona D.11 12030-RFP P25 Radio System Infrastructure Upgrade 48 VDC Battery Systems for AC-Powered Sites Sites with microwave or other equipment normally powered from a 48 VDC source shall have a 48 VDC (nominal) battery system. D.11.1 Battery Capacity Battery plants shall be sized to provide 8 hours of continuous operation with all loads operating at a 100% duty cycle. D.11.2 Battery Chemistry The battery systems shall utilize sealed lead-calcium cells rated for telecommunication service. Vendors may propose alternative battery chemistries that are superior to the one specified, if desired. D.11.2.1 Batteries shall be warranted by the manufacturer for a minimum of three years. D.11.3 Rectifiers/Chargers D.11.3.1 All critical components shall be modular and hot-swappable. D.11.3.2 Rectifiers/Chargers shall utilize a minimum of N+1 redundancy for all critical components. D.11.3.2.1 D.11.3.3 AC to DC conversion efficiency shall be a minimum of 88 percent. D.11.3.4 Power factor of 98 percent or greater. D.11.3.5 Output regulation shall be less than one percent for a load step from 50 percent to 100 percent. D.11.3.6 Output current rating of the Rectifier/Charger shall be a minimum of 150 percent of the load current draw. D.11.3.7 Protection Features Rectifiers/Chargers shall have the following protection features: D.11.3.8 D.11.3.7.1 Input and output circuit breakers D.11.3.7.2 Input transient protection D.11.3.7.3 Input inrush current limiting D.11.3.7.4 Output current limiting and short-circuit protection D.11.3.7.5 Over-temperature protection Front-Panel Indicators Rectifiers/Chargers shall have the following front-panel indicators: D.11.3.8.1 May 17, 2012 Failure of a single rectifier module shall not cause the ratings of the remaining modules to be exceeded or cause a fluctuation in output voltage or current. AC power input on/normal Document 2 - Specification & Response Document Page 86 of 399 Maricopa County, Arizona D.11.3.9 D.11.3.10 12030-RFP P25 Radio System Infrastructure Upgrade D.11.3.8.2 Output voltmeter with 0.1 V resolution D.11.3.8.3 Output ammeter with 0.1 A resolution D.11.3.8.4 Rectifier failure alarm (one per rectifier module) Remote Metering and Diagnostics All front panel indicators listed above shall be available remotely through the Diagnostic and Monitoring System specified in Section D.24 of this document. In addition, the following conditions shall also be monitored through the Diagnostic and Monitoring System: D.11.3.9.1 Output overvoltage alarm D.11.3.9.2 Output over-current alarm D.11.3.9.3 Battery charge and condition D.11.3.9.4 Over-temperature alarm Environmental and Mechanical D.11.3.10.1 Operating temperature 0 deg. C to +65 deg. C. D.11.3.10.2 Relative humidity 0 percent to 95 percent D.11.3.10.3 Altitude: Rectifiers/Chargers shall be rated at full specifications at the altitude at which it will be installed. D.11.3.10.4 Rectifiers/Chargers shall be mountable in a standard 19 inch EIA rack. D.11.4 Low-Voltage Disconnect An automatic low voltage disconnect device shall be provided to protect the batteries from damage due to excessive discharge. D.11.4.1 The Low-Voltage Disconnect device shall automatically disconnect the load from the source when the source voltage drops below a pre-set threshold, and automatically re-connect the load when the source voltage rises above a pre-set threshold. D.11.4.2 The disconnect and re-connect thresholds shall be independent and user-adjustable. D.11.4.3 Alarms The Low-Voltage Disconnect Device shall have alarm outputs for: D.11.4.4 May 17, 2012 D.11.4.3.1 Pre-Disconnection due to low voltage D.11.4.3.2 Disconnection due to low voltage The alarms listed above shall be available remotely through the Diagnostic and Monitoring System specified in Section D.24 of this document. Document 2 - Specification & Response Document Page 87 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.11.5 DC to DC Converters If more than one DC power voltage is needed, DC to DC converters shall be provided. D.11.5.1 Input and output circuits shall be isolated from each other and from the converter chassis. D.11.5.2 DC to DC converters shall be rated for continuous operation at full rated output current. D.11.5.3 Output current rating of the DC to DC converter shall be a minimum of 150 percent of the load current draw at 100 percent duty cycle. D.11.5.4 Output voltage regulation shall be +/- 1 percent or better for all input line and output load conditions. D.11.5.5 Output DC ripple shall be +/- 0.5 percent P-P or less. D.11.5.6 Conversion efficiency shall be 85 percent or greater. D.11.5.7 Protection Features DC to DC converters shall have the following protection features: D.11.5.8 D.11.5.9 D.11.5.7.1 Input and output fuses or circuit breakers. D.11.5.7.2 Output current limiting and short-circuit protection. D.11.5.7.3 Output overvoltage protection. D.11.5.7.4 Input overvoltage protection. D.11.5.7.5 Reverse polarity protection. D.11.5.7.6 High temperature protection. Front-Panel Indicators DC to DC Converters shall have the following front-panel indicators: D.11.5.8.1 Output Voltmeter D.11.5.8.2 Output Ammeter Remote Metering and Diagnostics All front panel indicators listed above shall be available remotely through the Diagnostic and Monitoring System specified in Section D.24 of this document. In addition, the following conditions shall also be monitored through the Diagnostic and Monitoring System: D.11.5.9.1 D.11.5.10 Environmental and Mechanical D.11.5.10.1 Operating temperature 0 deg. C to +50 deg. C. D.11.5.10.2 May 17, 2012 Major alarm Relative humidity 0 percent to 95 percent Document 2 - Specification & Response Document Page 88 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.11.5.10.3 DC to DC converters shall be rated at full specifications at the altitude at which it will be installed. D.11.5.10.4 DC to DC converters shall be mountable in a standard 19 inch EIA rack. D.11.6 DC to AC Inverters If AC voltages must be supplied from a DC source, DC to AC inverters shall be provided. D.11.6.1 Input and output circuits shall be isolated from each other and from the converter chassis. D.11.6.2 DC to AC inverters shall be rated for continuous operation at full rated output power. D.11.6.3 Output power rating of the DC to AC inverter shall be a minimum of 150 percent of the load power draw. D.11.6.4 Output voltage regulation shall be +/- 2 percent or better for all input line and output load conditions. D.11.6.5 Output shall be a pure sine wave with 4 percent distortion or less. D.11.6.6 Output frequency shall be 60 Hz +/- 0.5 Hz under all load conditions. D.11.6.7 Conversion efficiency shall be 90 percent or greater. D.11.6.8 Protection Features DC to AC inverters shall have the following protection features: D.11.6.9 D.11.6.10 May 17, 2012 D.11.6.8.1 Input and output fuses or circuit breakers. D.11.6.8.2 Output current limiting and short-circuit protection. D.11.6.8.3 Output overvoltage protection. D.11.6.8.4 Input overvoltage protection. D.11.6.8.5 High temperature protection. Front-Panel Indicators DC to DC Converters shall have the following front-panel indicators: D.11.6.9.1 Output voltmeter D.11.6.9.2 Output frequency D.11.6.9.3 Input voltmeter Remote Metering and Diagnostics All front panel indicators listed above shall be available remotely through the Diagnostic and Monitoring System specified in Section D.24 of this document. In addition, the following conditions shall also be monitored through the Diagnostic and Monitoring System: Document 2 - Specification & Response Document Page 89 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.11.6.10.1 D.11.6.11 Major alarm Environmental and Mechanical D.11.6.11.1 Operating temperature 0 deg. C to +50 deg. C. D.11.6.11.2 Relative humidity 0 percent to 95 percent D.11.6.11.3 DC to AC inverters shall be rated at full specifications at the altitude at which it will be installed. D.11.6.11.4 DC to AC inverters shall be mountable in a standard 19 inch EIA rack. D.11.7 DC Power Distribution D.11.7.1 The main DC power lead from the battery bank shall be protected by an appropriately rated fuse or circuit breaker. May 17, 2012 D.11.7.2 Each branch circuit shall also be protected by an appropriately rated fuse or circuit breaker. D.11.7.3 Branch circuit fuses and circuit breakers shall be aggregated into a single fuse panel or circuit breaker panel. D.11.7.3.1 Panels shall have space and capacity for a minimum of 30 percent growth in current load and the number of circuits installed. D.11.7.3.2 Differing voltages shall have separate panels. D.11.7.4 DC bus bars and other high-current conductors shall be shielded and protected against accidental contact by tools, jewelry or other conductive objects. D.11.7.5 Cables carrying DC power shall be jacketed. D.11.7.5.1 DC power cables shall be color-coded or clearly marked as to polarity (positive or negative) over their entire length. D.11.7.5.2 DC power cables carrying differing voltages shall be color-coded or marked differently from each other. Document 2 - Specification & Response Document Page 90 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.11 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.11 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Requirement Comply/ Section Exception D.11 D.11.1 D.11.2 D.11.2.1 D.11.3 D.11.3.1 D.11.3.2 D.11.3.2.1 D.11.3.3 D.11.3.4 D.11.3.5 D.11.3.6 D.11.3.7 D.11.3.7.1 D.11.3.7.2 D.11.3.7.3 D.11.3.7.4 D.11.3.7.5 D.11.3.8 D.11.3.8.1 D.11.3.8.2 D.11.3.8.3 D.11.3.8.4 D.11.3.9 D.11.3.9.1 D.11.3.9.2 D.11.3.9.3 D.11.3.9.4 D.11.3.10 D.11.3.10.1 D.11.3.10.2 D.11.3.10.3 May 17, 2012 Document 2 - Specification & Response Document Page 91 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.11 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.11.3.10.4 D.11.4 D.11.4.1 D.11.4.2 D.11.4.3 D.11.4.3.1 D.11.4.3.2 D.11.4.4 D.11.5 D.11.5.1 D.11.5.2 D.11.5.3 D.11.5.4 D.11.5.5 D.11.5.6 D.11.5.7 D.11.5.7.1 D.11.5.7.2 D.11.5.7.3 D.11.5.7.4 D.11.5.7.5 D.11.5.7.6 D.11.5.8 D.11.5.8.1 D.11.5.8.2 D.11.5.9 D.11.5.9.1 D.11.5.10 D.11.5.10.1 D.11.5.10.2 D.11.5.10.3 D.11.5.10.4 D.11.6 May 17, 2012 Document 2 - Specification & Response Document Page 92 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.11 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.11.6.1 D.11.6.2 D.11.6.3 D.11.6.4 D.11.6.5 D.11.6.6 D.11.6.7 D.11.6.8 D.11.6.8.1 D.11.6.8.2 D.11.6.8.3 D.11.6.8.4 D.11.6.8.5 D.11.6.9 D.11.6.9.1 D.11.6.9.2 D.11.6.9.3 D.11.6.10 D.11.6.10.1 D.11.6.11 D.11.6.11.1 D.11.6.11.2 D.11.6.11.3 D.11.6.11.4 D.11.7 D.11.7.1 D.11.7.2 D.11.7.3 D.11.7.3.1 D.11.7.3.2 D.11.7.4 D.11.7.5 D.11.7.5.1 May 17, 2012 Document 2 - Specification & Response Document Page 93 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.11 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Requirement Comply/ Section Exception D.11.7.5.2 {End Section D.11} May 17, 2012 Document 2 - Specification & Response Document Page 94 of 399 Maricopa County, Arizona D.12 12030-RFP P25 Radio System Infrastructure Upgrade Backup AC Power Generators All antenna sites powered by commercial AC shall be equipped with a backup AC power generator (unless otherwise directed by the County). Contractor shall provide Maricopa County with all information related to the specified internal combustion engines required for the County to file for a Stationary Engine Permit, including make, model, serial number, brake horsepower, and manufacture date. D.12.1 General D.12.1.1 The preferred manufacturer is Olympian. D.12.1.2 It is desired that the generator be equipped with a Ford or Chevrolet engine. D.12.1.3 Generators shall meet or exceed the requirements of Underwriter's Laboratories UL-2200 standard. D.12.2 Fuel D.12.2.1 D.12.2.2 Fuel shall be propane. Liquid phase fuel tank withdrawal system is required. D.12.2.2.1 D.12.3 Engine D.12.3.1 Measures shall be taken to prevent freeze-up of the vaporizer. Engine cooling shall be a pressurized, closed radiator-cooled system. D.12.3.1.1 The cooling system shall be filled with a water and coolant mixture in accordance with the engine manufacturer's recommendations. D.12.3.2 For generators installed at altitudes above 3000 feet, a thermostatically controlled water jacket coolant heater shall be provided and installed in accordance with the manufacturer's recommendations. D.12.3.3 Engine electrical system shall be 12 VDC, negative ground. D.12.4 Outdoor Installation Generators shall be configured for outdoor installation. May 17, 2012 D.12.4.1 The generator set shall be mounted on a heavy duty steel base. D.12.4.2 The base shall maintain alignment between generator set components and shall include vibration isolators. D.12.4.3 The generator steel base shall be set on a concrete foundation and securely bolted to the foundation. D.12.4.4 Enclosure shall be of steel construction. Document 2 - Specification & Response Document Page 95 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.4.5 In areas within 0.25 mile of residential dwellings, the enclosure shall incorporate additional sound attenuation features to prevent complaints from residents. D.12.4.6 Generators located at 3,000 feet AMSL or above shall be protected from falling ice by a steel ice shield. D.12.5 Furnished Complete Generators shall be furnished complete with all accessories and equipment needed for the proper operation of the unit, including but not limited to: D.12.5.1 Vermin-resistant outdoor cabinet D.12.5.2 A 12 VDC starting battery sized appropriately for the engine/generator combination being provided D.12.5.3 A battery rack D.12.5.4 A battery charger D.12.5.5 Battery cables D.12.5.6 Cooling system D.12.5.7 Residential grade exhaust silencer with exhaust pipe, USFS-approved spark arrestor and rain cap D.12.5.8 Automatic load transfer switch and controls D.12.5.9 Electrical surge protection D.12.5.10 Automatic output frequency regulation D.12.5.11 Vibration isolators D.12.5.12 Fuel storage tank with remote-indicating fuel gauge D.12.5.13 Fuel lines D.12.5.14 Fuel pressure regulator D.12.5.15 Fuel filter/water separator D.12.5.16 Fuel vaporizer D.12.5.17 Electrical wiring, conduits and, junction boxes D.12.5.18 Instrument panel D.12.6 Ratings D.12.6.1 D.12.6.2 May 17, 2012 Output power rating of the generator shall be sufficient to support 150% of the full forecasted load of the Site. Altitude 7500 feet AMSL or less at each site. Document 2 - Specification & Response Document Page 96 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.6.3 Ambient temperature between 0 degrees and 120 degrees Fahrenheit. D.12.6.4 Output voltage regulation +/- 0.5 percent of rated voltage for constant load between no load and full load. D.12.6.5 Output frequency regulation 60 Hz +/- 0.5 percent from steady state no load to steady state rated load. D.12.6.6 Single Step Load Pickup: 100 percent of rated output power, less applicable de-rating factors, with the engine-generator at operating temperature. D.12.6.7 Generator shall be factory tested at 100% load for 3 hours D.12.7 Generator Set Control The generator shall be equipped with automatic start, manual local start and manual remote start type compatible with the automatic transfer switch to be supplied with the generator. Manual starting and stopping controls shall be provided via: D.12.7.1 The generator front panel controls D.12.7.2 The transfer switch controls D.12.7.3 The Diagnostic and Monitoring System specified in Section D.24 of this document. D.12.8 Cranking Control The generator control system shall provide a minimum of three cranking cycles of at least 15 seconds before lockout and activation of an overcrank alarm condition. D.12.9 Generator Protection Controls (per NFPA-110) Generators shall shut down and lock out upon: D.12.9.1 Failure to start (overcrank) D.12.9.2 Over-speed D.12.9.3 Low lubricating oil pressure D.12.9.4 High engine temperature D.12.10 Generator/Transfer Switch Alarms Dry contact alarm outputs shall be provided for the following conditions: May 17, 2012 D.12.10.1 Failure to start (overcrank) D.12.10.2 Over-speed D.12.10.3 Low lubricating oil pressure D.12.10.4 Low lubricating oil pressure pre-warning D.12.10.5 High engine temperature D.12.10.6 Low coolant Document 2 - Specification & Response Document Page 97 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.10.7 Generator engine run D.12.10.8 Generator on-line D.12.10.9 Low starting battery voltage D.12.10.10 High starting battery voltage D.12.10.11 Low fuel D.12.11 Generator Front Panel Metering Meters shall be provided on the generator to indicate: D.12.11.1 AC output voltage D.12.11.2 AC output current D.12.11.3 AC output frequency D.12.11.4 Engine RPM D.12.11.5 Engine running time D.12.12 Generator Front Panel Controls D.12.12.1 Engine start D.12.12.2 Engine stop D.12.12.3 AC output voltage adjust D.12.13 Generator Fuel Tank The Contractor shall supply a new, fully primed and painted propane fuel storage tank(s) at each Site where a new generator will be placed. May 17, 2012 D.12.13.1 The fuel tank(s) shall have a capacity sufficient to run the generator for a minimum of one week at full load. D.12.13.2 The fuel tank shall be installed within the Site fenced perimeter in a location easily accessible for re-fueling. D.12.13.3 The fuel tank shall be set on a concrete foundation and securely bolted to the foundation. D.12.13.4 The Contractor shall provide all necessary hardware and supplies for fuel tank installation. D.12.13.5 The fuel tank and its installation shall meet all applicable codes, standards, laws and requirements and shall be installed using best industry practices. D.12.13.6 The fuel tank shall be equipped with a remote fuel level monitoring system. Fuel tank levels shall be available through the Diagnostic and Monitoring System specified in Section D.24 of this document. Document 2 - Specification & Response Document Page 98 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.13.7 If required by codes, ordinances, laws or regulations, the Contractor shall supply and install fuel leak detectors which will send leak alarms to the Diagnostic and Monitoring System specified in Section D.24 of this document. D.12.13.8 The Contractor shall fill the fuel tank to capacity upon acceptance of the site by the County. D.12.14 Transfer Switch An automatic transfer switch to provide switching of the electrical load between commercial power and generator power shall be provided and installed for each generator set. May 17, 2012 D.12.14.1 The transfer switch shall be completely factory assembled. D.12.14.2 The transfer switch shall contain electronic controls designed for surge voltage isolation, with voltage sensors on all phases of both the normal and emergency input power sources. D.12.14.3 The transfer switch shall be installed in a key locking, UL listed, NEMA dust and moisture-proof cabinet. D.12.14.4 The transfer switch shall be mounted on an interior wall of the equipment space. D.12.14.5 The transfer switch shall be fully wired and integrated with the engine generator set in accordance with the manufacturer's instructions and applicable electrical and fire codes. D.12.14.6 Transfer switches and accessories shall be U.L. listed and labeled, tested per U.L. Standard 1008 and CSA Approved. D.12.14.7 The switch shall provide double-throw, positive mechanical and electrical interlocking and mechanically held contacts. D.12.14.8 Main switch contacts shall be high pressure silver alloy. D.12.14.9 Contact assemblies shall have arc chutes for positive arc extinguishment. Arc chutes shall have insulating covers to prevent interphase flashover. D.12.14.10 Permanently attached manual control handles shall also be installed on the transfer switch. Quick-make and quick-break contact mechanisms shall be provided for manual transfer under load. D.12.14.11 Form C contacts shall be provided in each position for alarm reporting purposes. Document 2 - Specification & Response Document Page 99 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.14.11.1 May 17, 2012 These contacts shall be connected to the Diagnostic and Monitoring System specified in Section D.24 of this document for reporting transfer status. D.12.14.12 The transfer switch shall be rated for continuous operation in ambient temperatures from 0 degrees to 120 degrees Fahrenheit. D.12.14.13 Transfer switches shall be rated to carry 100% of the current rating of the commercial AC power feed (for example, if the power company is providing 200 A service to the site, the transfer switch shall be rated at 200 A). D.12.14.14 Transfer switch control shall be solid state and designed for a high level of immunity to power line surges and transients. D.12.14.15 Transfer switch controls shall have optically isolated logic inputs, and isolation transformers for AC inputs. Relays shall be installed on all outputs. D.12.14.16 The transfer switch shall be tested in accordance with IEEE Standard 587-1980 (or latest revision). D.12.14.17 Solid-state under voltage sensors shall simultaneously monitor all phases of each power source. D.12.14.17.1 Pick up and drop out voltage settings shall be adjustable. D.12.14.17.2 Voltage sensors shall allow for adjustment to sense partial loss of voltage on any phase. D.12.14.18 Transfer switches shall be provided with solid-state over-voltage sensors, adjustable from 100-130% of nominal input voltage to monitor the source. D.12.14.19 Automatic controls shall signal the engine-generator to start upon signal from normal source sensors. D.12.14.19.1 A time delay start, variable from at least 0 to 5 seconds, shall be provided to avoid nuisance start ups. D.12.14.19.2 The switch shall transfer when the emergency source stabilizes at the set point voltage and frequency. A time delay shall be provided for transfer, which is variable from 0 to 120 seconds. D.12.14.19.3 The switch shall retransfer the load to the normal source after the normal source stabilizes at the normal voltage and frequency, after an adjustable time delay. Document 2 - Specification & Response Document Page 100 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.14.20 D.12.14.21 D.12.14.22 May 17, 2012 D.12.14.19.4 The retransfer time delay shall be immediately bypassed if the emergency generator fails. D.12.14.19.5 A control shall automatically signal the generator engine to stop after a time delay, which shall be adjustable from at least 0 to 10 minutes, the time delay period beginning upon re-transfer to commercial power. D.12.14.19.6 Power for transfer operation shall be from the source to which the load is being transferred. The transfer switch shall be equipped with a programmable exerciser clock which allows setting the day, time and duration of a generator set exercise/test period. D.12.14.20.1 Tests under load or with no load shall be selectable. D.12.14.20.2 Control of the above parameters shall be available through the Alarm and Diagnostic Subsystem described in Section D.24. In the event of a failed transfer operation, diagnostic indicators shall be provided to allow the last successful step in the sequence of control functions to be pinpointed. The present status of the control functions shall also be indicated. These functions, at a minimum, shall include: D.12.14.21.1 Source 1 OK D.12.14.21.2 Generator engine start D.12.14.21.3 Source 2 OK D.12.14.21.4 Transfer timing D.12.14.21.5 Transfer complete D.12.14.21.6 Retransfer timing D.12.14.21.7 Retransfer complete D.12.14.21.8 Timing for stop A key operated selector switch shall be provided which will provide the following functions: D.12.14.22.1 Test: to simulate commercial power loss to allow testing of the generator set with or without transfer of the load. D.12.14.22.2 Normal: leaves the switch in its normal operating position. Document 2 - Specification & Response Document Page 101 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.12.14.22.3 Retransfer: a momentary position, which will provide an override of the retransfer time delay and cause immediate return to the commercial power source (if available). D.12.15 Start-Up Service A factory authorized service representative shall provide initial start up service for each new generator that is installed. May 17, 2012 Document 2 - Specification & Response Document Page 102 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.12 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.12 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.12 D.12.1 D.12.1.1 D.12.1.2 D.12.1.3 D.12.2 D.12.2.1 D.12.2.2 D.12.2.2.1 D.12.3 D.12.3.1 D.12.3.1.1 D.12.3.2 D.12.3.3 D.12.4 D.12.4.1 D.12.4.2 D.12.4.3 D.12.4.4 D.12.4.5 D.12.4.6 D.12.5 D.12.5.1 D.12.5.2 D.12.5.3 D.12.5.4 D.12.5.5 D.12.5.6 D.12.5.7 D.12.5.8 D.12.5.9 D.12.5.10 May 17, 2012 Document 2 - Specification & Response Document Page 103 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.12 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.12.5.11 D.12.5.12 D.12.5.13 D.12.5.14 D.12.5.15 D.12.5.16 D.12.5.17 D.12.5.18 D.12.6 D.12.6.1 D.12.6.2 D.12.6.3 D.12.6.4 D.12.6.5 D.12.6.6 D.12.6.7 D.12.7 D.12.7.1 D.12.7.2 D.12.7.3 D.12.8 D.12.9 D.12.9.1 D.12.9.2 D.12.9.3 D.12.9.4 D.12.10 D.12.10.1 D.12.10.2 D.12.10.3 D.12.10.4 D.12.10.5 D.12.10.6 May 17, 2012 Document 2 - Specification & Response Document Page 104 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.12 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.12.10.7 D.12.10.8 D.12.10.9 D.12.10.10 D.12.10.11 D.12.11 D.12.11.1 D.12.11.2 D.12.11.3 D.12.11.4 D.12.11.5 D.12.12 D.12.12.1 D.12.12.2 D.12.12.3 D.12.13 D.12.13.1 D.12.13.2 D.12.13.3 D.12.13.4 D.12.13.5 D.12.13.6 D.12.13.7 D.12.13.8 D.12.14 D.12.14.1 D.12.14.2 D.12.14.3 D.12.14.4 D.12.14.5 D.12.14.6 D.12.14.7 D.12.14.8 May 17, 2012 Document 2 - Specification & Response Document Page 105 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.12 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.12.14.9 D.12.14.10 D.12.14.11 D.12.14.11.1 D.12.14.12 D.12.14.13 D.12.14.14 D.12.14.15 D.12.14.16 D.12.14.17 D.12.14.17.1 D.12.14.17.2 D.12.14.18 D.12.14.19 D.12.14.19.1 D.12.14.19.2 D.12.14.19.3 D.12.14.19.4 D.12.14.19.5 D.12.14.19.6 D.12.14.20 D.12.14.20.1 D.12.14.20.2 D.12.14.21 D.12.14.21.1 D.12.14.21.2 D.12.14.21.3 D.12.14.21.4 D.12.14.21.5 D.12.14.21.6 D.12.14.21.7 D.12.14.21.8 D.12.14.22 May 17, 2012 Document 2 - Specification & Response Document Page 106 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.12 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Standard Standard Standard Standard Requirement Comply/ Section Exception D.12.14.22.1 D.12.14.22.2 D.12.14.22.3 D.12.15 {End Section D.12} May 17, 2012 Document 2 - Specification & Response Document Page 107 of 399 Maricopa County, Arizona D.13 12030-RFP P25 Radio System Infrastructure Upgrade Uninterruptible Power Supplies Sites with critical components operating from AC power shall include an Uninterruptible Power Supply ("UPS") to protect the critical components from failure and damage during a power outage and to keep the site operational while the backup generator comes on-line. D.13.1 Modular Critical components of the UPS shall be modular to permit redundancy and scalability. D.13.2 User-Replaceable, Hot-Swappable Modules Critical modular components of the UPS shall be user replaceable and hot-swappable under full load. D.13.3 Capacity of UPS UPS shall be sized to accommodate the power draw of all AC-powered components (operating at 100% duty cycle) necessary to keep the site fully operational during a failure of primary AC power, plus an additional 50% for future growth. D.13.4 Runtime D.13.4.1 Batteries at simulcast prime sites and Sites located at greater than a two-hour drive time from the Durango Complex shall be sized to provide a four hour runtime following loss of AC input power with all AC-powered components operating at 100% duty cycle. D.13.4.2 Batteries at all other Sites shall be sized for a two-hour runtime. D.13.5 Redundancy D.13.5.1 Critical modular components of the UPS shall have a minimum of N+1 redundancy. D.13.5.2 Failure of a single module shall not cause the ratings of the remaining modules to be exceeded or cause a fluctuation in output voltage or current. D.13.5.3 Failed modules shall be automatically isolated from the affected circuit(s) to prevent damage to other modules or circuits. D.13.6 Bypass Switch D.13.6.1 The UPS shall include an internal automatic bypass switch that puts the UPS in bypass mode when the UPS AC power output fails or becomes significantly degraded. D.13.6.2 The UPS shall also have a manual bypass switch that completely bypasses the UPS for maintenance and repair purposes. D.13.7 Modes of Operation D.13.7.1 Normal The input converter and output inverter shall operate in an on-line manner to continuously regulate power to the critical load. The input and output converters shall be equipped to fully recharge the battery May 17, 2012 Document 2 - Specification & Response Document Page 108 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade while simultaneously providing regulated power to the load for all line and load conditions within the range of the UPS specifications. D.13.7.2 Battery Upon failure of the AC input source, the critical load shall continue being supplied by the output inverter, which shall derive its power from the battery system. There shall be no interruption in power to the critical load during both transfers to battery operation and retransfers from battery to normal operation. D.13.7.3 Recharge Upon restoration of the AC input source, the input converter and output inverter shall simultaneously recharge the battery and provide regulated power to the critical load. D.13.7.4 Automatic Bypass The automatic bypass shall automatically transfer the critical load from the Inverter output to the bypass source in the event of failure or significant degradation of the UPS AC output power. This transfer, along with its retransfer, shall take place with no power interruption to the critical load. The automatic bypass shall be configured to "wrap around" the power modules (rectifier, battery charger, inverter), and battery modules while still supplying surge protection, EMI filtering, and over-current protection. D.13.7.5 Manual Bypass (Internal) The system shall be equipped with an internal make-before-break two pole switch to electrically isolate the UPS from the input and output during preventative maintenance, module upgrades, or limited service. The internal manual bypass shall be configured to "wrap around" the power modules (rectifier, battery charger, inverter), and battery modules in the same manner as the automatic bypass while still supplying surge protection, EMI filtering, and over-current protection. D.13.7.6 Manual Bypass (External) The system shall be equipped with an external make-before-break two pole switch to completely electrically isolate the UPS from the input and output during preventative maintenance and repairs. This mode shall also bypass the surge protection, EMI filtering, and over-current protection. D.13.8 Ratings D.13.8.1 May 17, 2012 AC Input D.13.8.1.1 Nominal AC Voltage and Phase: As required by individual site conditions. Document 2 - Specification & Response Document Page 109 of 399 Maricopa County, Arizona D.13.8.2 12030-RFP P25 Radio System Infrastructure Upgrade D.13.8.1.2 AC Input Voltage Range: +/- 15% of nominal without degradation to output voltage, current or waveform. D.13.8.1.3 Input Frequency: 47 Hz to 63 Hz D.13.8.1.4 Input Power Factor: .95 AC Output D.13.8.2.1 Output Voltage and Phase: 120 VAC, single phase. D.13.8.2.2 Output Voltage Distortion: 2% maximum under a linear 100% load, 5% maximum under a non-linear 100% load. D.13.8.2.3 Output Voltage Regulation: +/- 3% under full load. D.13.8.2.4 Output Voltage Transient Response: +/- 5% maximum for 100% load step. D.13.8.2.5 Voltage Transient Recovery Time: <60 ms maximum. D.13.8.2.6 Overload Rating: 130% for 4 seconds, minimum. D.13.8.2.7 Input voltage anomalies such as brown-outs, spikes, surges, sags, and outages shall not affect the UPS output. D.13.8.3 AC to AC conversion efficiency shall be a minimum of 83 percent. D.13.8.4 Environmental D.13.8.4.1 Operating Ambient Temperature: 0 to +120 deg. F. D.13.9 Batteries D.13.9.1 D.13.8.4.2 Relative Humidity: 5% to 95%, non-condensing. D.13.8.4.3 Altitude: UPS shall meet all specifications at the altitude at which it will be installed. D.13.8.4.4 Audible Noise: <55 dB at 1 meter. The UPS shall monitor battery temperature and condition. D.13.9.2 The UPS shall regulate the battery charging current to optimize battery life. D.13.9.3 The UPS shall monitor the level of battery discharge and shall automatically prevent damage to batteries due to excessive discharge. D.13.9.4 The UPS shall generate an alarm when a battery cell has failed or is in poor condition. D.13.10 Metering and Diagnostics D.13.10.1 Front-Panel Metering The following meters/displays shall be available at the UPS front panel: May 17, 2012 Document 2 - Specification & Response Document Page 110 of 399 Maricopa County, Arizona D.13.10.2 D.13.10.3 D.13.10.4 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.13.10.1.1 Time and date. D.13.10.1.2 AC input Voltage. D.13.10.1.3 AC input current. D.13.10.1.4 AC input frequency. D.13.10.1.5 Battery Voltage. D.13.10.1.6 Battery temperature. D.13.10.1.7 AC output Voltage. D.13.10.1.8 AC output current. Front-Panel Indicators The following indicators shall be available at the UPS front panel: D.13.10.2.1 Current operating mode (normal, battery, internal bypass). D.13.10.2.2 AC input Voltage high/low alarms. D.13.10.2.3 AC input over-current alarm. D.13.10.2.4 Battery DC voltage high/low alarms. D.13.10.2.5 Rectifier DC Voltage high/low alarms. D.13.10.2.6 Rectifier over-current alarm. D.13.10.2.7 Rectifier failure alarm. D.13.10.2.8 Battery cell failure alarm. D.13.10.2.9 Poor battery health alarm. D.13.10.2.10 AC output Voltage high/low alarms. D.13.10.2.11 AC output over-current alarm. D.13.10.2.12 Inverter failure alarm. D.13.10.2.13 Remaining battery backup time (in minutes). Front-Panel Controls The following controls shall be available from the UPS front panel: D.13.10.3.1 Set date and time. D.13.10.3.2 Initiate manual bypass and re-transfer back to battery. D.13.10.3.3 Reset alarms. Status and Event Log The UPS shall maintain an Event Log which records an entry whenever the UPS changes operating mode status or an alarm occurs. Document 2 - Specification & Response Document Page 111 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.13.10.4.1 D.13.10.5 The Event Log shall also record periodic measurements of: D.13.10.4.1.1 AC input Voltage. D.13.10.4.1.2 AC input current. D.13.10.4.1.3 DC battery Voltage. D.13.10.4.1.4 AC output Voltage. D.13.10.4.1.5 AC output current. D.13.10.4.2 Measurement intervals shall be adjustable by the user. D.13.10.4.3 The Event Log shall be accessible via a front panel display. All meters, indicators, alarms and the Event Log shall be available remotely through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.13.11 Start-Up Service A factory authorized service representative shall provide initial start up service for each new UPS that is installed. May 17, 2012 Document 2 - Specification & Response Document Page 112 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.13 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.13 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Requirement Comply/ Section Exception D.13 D.13.1 D.13.2 D.13.3 D.13.4 D.13.4.1 D.13.4.2 D.13.5 D.13.5.1 D.13.5.2 D.13.5.3 D.13.6 D.13.6.1 D.13.6.2 D.13.7 D.13.7.1 D.13.7.2 D.13.7.3 D.13.7.4 D.13.7.5 D.13.7.6 D.13.8 D.13.8.1 D.13.8.1.1 D.13.8.1.2 D.13.8.1.3 D.13.8.1.4 D.13.8.2 D.13.8.2.1 D.13.8.2.2 D.13.8.2.3 D.13.8.2.4 May 17, 2012 Document 2 - Specification & Response Document Page 113 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.13 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.13.8.2.5 D.13.8.2.6 D.13.8.2.7 D.13.8.3 D.13.8.4 D.13.8.4.1 D.13.8.4.2 D.13.8.4.3 D.13.8.4.4 D.13.9 D.13.9.1 D.13.9.2 D.13.9.3 D.13.9.4 D.13.10 D.13.10.1 D.13.10.1.1 D.13.10.1.2 D.13.10.1.3 D.13.10.1.4 D.13.10.1.5 D.13.10.1.6 D.13.10.1.7 D.13.10.1.8 D.13.10.2 D.13.10.2.1 D.13.10.2.2 D.13.10.2.3 D.13.10.2.4 D.13.10.2.5 D.13.10.2.6 D.13.10.2.7 D.13.10.2.8 May 17, 2012 Document 2 - Specification & Response Document Page 114 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.13 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.13.10.2.9 D.13.10.2.10 D.13.10.2.11 D.13.10.2.12 D.13.10.2.13 D.13.10.3 D.13.10.3.1 D.13.10.3.2 D.13.10.3.3 D.13.10.4 D.13.10.4.1 D.13.10.4.1.1 D.13.10.4.1.2 D.13.10.4.1.3 D.13.10.4.1.4 D.13.10.4.1.5 D.13.10.4.2 D.13.10.4.3 D.13.10.5 D.13.11 {End Section D.13} May 17, 2012 Document 2 - Specification & Response Document Page 115 of 399 Maricopa County, Arizona D.14 12030-RFP P25 Radio System Infrastructure Upgrade Antenna Support Structures D.14.1 New Antenna Support Structures The Contractor shall provide and construct new towers, monopoles or other types of antenna support structures at new sites that do not have an existing antenna support structure, and at sites with existing antenna support structures that do not meet and cannot be modified to meet the requirements of this Section D.14. D.14.2 Existing Antenna Support Structures At sites with existing towers, monopoles or other antenna support structures, the Contractor shall modify the existing structure to meet the applicable requirements of this Section D.14. D.14.2.1 The structure and foundation shall be strengthened if required. D.14.2.2 The height of the structure shall be increased if required. D.14.2.3 Items required by this Section D.14 that are not present on the existing structure (examples: cable ladder and obstruction lighting) shall be added. D.14.2.4 At sites where the existing structure cannot be modified to meet the requirements of this Section D.14, the Contractor shall provide and construct a new structure. D.14.2.4.1 Upon completion of the new structure, the Contractor shall transfer all antennas and appurtenances from the old structure to the new structure. D.14.2.4.2 Upon completion of transfer of antennas and appurtenances to the new structure, the Contractor shall dismantle and remove the old structure. Disposition of the old structure materials shall be at the discretion of the County. D.14.3 Standards Towers, monopoles and other antenna support structures shall comply with: D.14.3.1 TIA-222-G (or latest revision), except as may otherwise be stated in this RFP. D.14.3.2 All applicable state, County and local building codes and ordinances. D.14.4 Materials D.14.4.1 May 17, 2012 All parts and materials shall be specifically designed for their intended use. D.14.4.2 All parts and materials shall be new. D.14.4.3 Towers and antenna support structures shall be of all-steel construction. Document 2 - Specification & Response Document Page 116 of 399 Maricopa County, Arizona D.4.14.4 12030-RFP P25 Radio System Infrastructure Upgrade Steel parts and materials shall be galvanized in accordance with TIA222-G. D.14.5 Height Height of towers and other antenna support structures shall be according to the Contractor's Detailed Design Document, as described elsewhere in this RFP. D.14.6 Loads, Stresses and Other Design Considerations D.14.6.1 The design of the structure shall take into account dead and live loads induced by the structure itself and all antennas and appurtenances, and all stress applied to the tower and its appurtenances by wind and seismic forces. The minimum safety factors specified in TIA-222-G shall apply under the most severe combination of dead load plus live loading. D.14.6.2 In the case of new structures, the design of each structure shall account for all antennas, transmission lines, mounts, brackets, supports, ladders, lighting and safety equipment that will be placed on the structure by the new Radio System, plus the following additional antennas and transmission lines for installation at a future date: D.14.6.2.1 Two eight-foot diameter parabolic dish antennas with radomes and the appropriate mounting brackets at a level three-quarters of the height of the structure, plus one run of Commscope EW63 elliptical waveguide for each antenna. D.14.6.2.2 Two 700 MHz panel antennas, Amphenol BXA-700408CF with the appropriate mounting brackets at the top of the structure, plus one run of 1-5/8" Commscope AVA series coaxial cable for each antenna. D.14.6.2.3 Optional Additional Capacity for Future Growth At the discretion of the County, the County may elect to delete the requirements of D.14.6.2.2 and replace them with the following: D.14.6.2.3.1 May 17, 2012 A triangular antenna support frame at the top of the tower, with four 700 MHz panel antennas, Amphenol BXA-700408CF with the appropriate mounting brackets on each face (12 antennas total), plus one run of 1-5/8" Commscope AVA series coaxial cable for each antenna. Document 2 - Specification & Response Document Page 117 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.14.6.2.4 D.14.6.3 The requirements for future antennas shall not apply to antenna support structures for Mini-Sites and MicroSites. In the case of existing structures that are to be modified, the design of each structure shall account for all antennas, transmission lines, mounts, brackets, supports, ladders, lighting and safety equipment that will be placed on the structure by the new Radio System, plus the existing antennas, transmission lines, mounts, brackets and supports that are to be transferred from the old structure to the new structure. In the case of existing structures that are owned or managed by the County, the design of the structure shall additionally account for the following antennas and transmission lines for installation at a future date: D.14.6.3.1 Two eight-foot diameter parabolic dish antennas with radomes and the appropriate mounting brackets at a level three-quarters of the height of the structure, plus one run of Commscope EW63 elliptical waveguide for each antenna. D.14.6.3.2 Two 700 MHz panel antennas, Amphenol BXA-700408CF with the appropriate mounting brackets at the top of the structure, plus one run of 1-5/8" Commscope AVA series coaxial cable for each antenna. D.14.6.3.3 Optional Additional Capacity for Future Growth At the discretion of the County, the County may elect to delete the requirements of D.14.6.3.2 and replace them with the following: D.14.6.3.3.1 D.14.6.4 May 17, 2012 A triangular antenna support frame at the top of the tower, with four 700 MHz panel antennas, Amphenol BXA-700408CF with the appropriate mounting brackets on each face (12 antennas total), plus one run of 1-5/8" Commscope AVA series coaxial cable for each antenna. Basic Wind Speed The Minimum Basic Wind Speed for Maricopa County, Arizona listed in Annex B of TIA-222-G (90 MPH) shall be used as the Basic Wind Speed for all antenna structure designs (including the strengthening of existing structures), except for the following locations which shall use a Basic Wind Speed of 100 MPH: Document 2 - Specification & Response Document Page 118 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.14.6.4.1 Durango D.14.6.4.2 Central Courts Building D.14.6.4.3 Emergency Management D.14.6.4.4 Thompson Peak D.14.6.4.5 Mount Gillen (Far North) D.14.6.4.6 White Tanks East D.14.6.4.7 Oatman Mountain D.14.6.5 Ice Loads Antenna support structures located at 3,000 feet AMSL or above shall additionally be designed for 1/2" of radial ice accumulation. D.14.6.6 Structure Classification All antenna support structures, new and existing, shall be considered to be Class III structures used primarily for essential communications, as defined in TIA-222-G. D.14.6.7 Exposure Category, Topographic Category and Site Class Antenna support structures shall be designed based on the appropriate Exposure Category, Topographic Category and Site Class (as defined in TIA-222-G) for the location selected. D.14.6.8 Foundations D.14.6.8.1 D.14.6.8.2 D.14.6.9 May 17, 2012 Foundations shall be designed to prevent damage and premature failure due to the effects of corrosive soil. The Geotechnical Report shall describe any corrosive soil conditions. Twist and Sway The Contractor shall specify acceptable twist and sway limits for each antenna support structure based upon the required reliability of the communications equipment that will be installed upon it (including all future requirements specified in this RFP). D.14.6.9.1 D.14.6.10 Foundations shall be designed based upon actual soil conditions found at the site as described in the Geotechnical Report for the specific site. The default value of 10 dB degradation specified in Annex A, paragraph A.2.8 of TIA-222-G shall not be used unless specifically approved by the Contractor. Climbing and Working Facilities Climbing and working facilities shall be designed as Class A (both basic and skilled climbers) as defined in TIA-222-G. Document 2 - Specification & Response Document Page 119 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.14.7 Cable Ladders A minimum of one cable ladder shall be supplied on each antenna support structure for attachment and support of transmission lines. D.14.7.1 Cable ladders shall have sufficient capacity to support all transmission lines for the antennas specified in D.14.6.2 and D.14.6.3. D.14.7.2 Cable ladder cross-pieces shall be spaced sufficiently close so that the transmission line manufacturer's maximum cable hanger spacing for a wind speed of 100 MPH will not be exceeded. D.14.7.3 Cable ladders shall be installed from a point no higher than the point the lowest transmission line will attach to the structure to the top of the structure. D.14.7.4 Multiple cable ladders shall be installed if necessary to accommodate all transmission lines (including all future requirements specified in this RFP). D.14.7.5 The cable ladder shall be of galvanized steel construction, and shall have mounting hardware of stainless steel or galvanized steel construction. D.14.7.5.1 May 17, 2012 In no case shall there be metal-to-metal combinations that result in rust or corrosion due to galvanic action. D.14.7.6 No drilling of structural members shall be required to securely attach the cable ladder to the structure. D.14.7.7 Transmission Line Attachment D.14.7.7.1 Transmission lines shall not be attached to any part of the antenna support structure other than the cable ladder. D.14.7.7.2 Transmission lines shall be installed to minimize antenna structure wind loading. D.14.7.7.3 Transmission lines shall be attached to the cable ladder using stainless steel hangers that are the manufacturer's recommended hanger for the type of cable being attached. D.14.7.7.4 Transmission lines shall be attached to the cable ladder at intervals no greater than that specified by the cable manufacturer for the specific cable being attached at at wind speed of 100 MPH. Document 2 - Specification & Response Document Page 120 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.14.8 Obstruction Lighting and Marking Antenna support structures shall be lighted and/or marked in accordance with the applicable chapters of FAA Advisory Circular AC 70/7460-1K, or latest revision, as required by the particular Aeronautical Study performed by the FAA for each structure. D.14.8.1 All obstruction lighting systems shall utilize LED technology for side lights and beacons. D.14.8.2 Activation of obstruction lighting systems shall be via a light sensitive, photoelectric type switch and controller which will activate the lights at dusk (or cloud darkened condition) and extinguish the lights at sunrise, in accordance with FAA and FCC requirements. D.14.8.2.1 The photoelectric device shall be mounted outdoors. D.14.8.2.2 The control circuitry shall be located indoors, either in an enclosure mounted in an easily-accessible location on a wall, or rack-mounted in a 19" EIA rack. D.14.8.3 If a dual lighting system is required at any site, the controller shall automatically switch at sunrise from red lights to strobe lights, and back to red lights when the sky darkens. D.14.8.4 The lighting control system shall be equipped to provide a single, form "C" dry contact closure alarm indication of bulb failure. D.14.8.4.1 D.14.8.5 Wiring for obstruction lighting shall be provided and installed in conformance with the lighting manufacturer's specifications and in accordance with local electrical codes. D.14.8.5.1 D.14.8.6 Wiring shall be enclosed in conduit. The obstruction lighting control shall be equipped with surge arrestors which will prevent a lightning strike to the structure or lighting system from damaging the controller. D.14.8.6.1 May 17, 2012 Upon bulb failure, the alarm condition shall be reported by the Diagnostic and Monitoring System specified in Section D.24 of this document. An acceptable protector is Quality Power Systems, LLC model (OLF-TWR-EIDB) or equivalent. D.14.8.7 The obstruction lighting system shall be designed to suppress all harmful RF interference. The Contractor shall include any optional components or circuitry required to eliminate RF interference. D.14.8.8 Temporary Obstruction Lighting During Construction The Contractor shall provide temporary obstruction lighting during construction if required. Document 2 - Specification & Response Document Page 121 of 399 Maricopa County, Arizona D.14.8.9 12030-RFP P25 Radio System Infrastructure Upgrade All obstruction lighting systems shall conform to all FAA, NEC, and FCC Regulations. D.14.9 Ice Shields Structures located at 3,000 feet AMSL or above shall be equipped with steel mesh ice shields installed above each of the microwave antennas to protect them from falling ice. The ice shield shall cover the width and depth of the microwave antenna it is intended to protect. D.14.10 Climbing Ladder Antenna support structures greater than 10 feet in height shall be provided with a climbing ladder including an OSHA-approved climbing safety device. May 17, 2012 D.14.10.1 The climbing ladder shall be attached to tower legs in a manner that does not interfere with the installation or maintenance of antennas and transmission lines. Similarly, the placement of cable ladder(s) shall not interfere with the climbing facility. D.14.10.2 The climbing ladder and climbing safety device shall include security features to prevent climbing by unauthorized persons. D.14.10.3 No drilling of structural members shall be required to securely attach the climbing ladder to the structure. Document 2 - Specification & Response Document Page 122 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.14 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.14 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.14 D.14.1 D.14.2 D.14.2.1 D.14.2.2 D.14.2.3 D.14.2.4 D.14.2.4.1 D.14.2.4.2 D.14.3 D.14.3.1 D.14.3.2 D.14.4 D.14.4.1 D.14.4.2 D.14.4.3 D.14.4.4 D.14.5 D.14.6 D.14.6.1 D.14.6.2 D.14.6.2.1 D.14.6.2.2 D.14.6.2.3 D.14.6.2.3.1 D.14.6.2.4 D.14.6.3 D.14.6.3.1 D.14.6.3.2 D.14.6.3.3 D.14.6.3.3.1 D.14.6.4 May 17, 2012 Document 2 - Specification & Response Document Page 123 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.14 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.14.6.4.1 D.14.6.4.2 D.14.6.4.3 D.14.6.4.4 D.14.6.4.5 D.14.6.4.6 D.14.6.4.7 D.14.6.5 D.14.6.6 D.14.6.7 D.14.6.8 D.14.6.8.1 D.14.6.8.2 D.14.6.9 D.14.6.9.1 D.14.6.10 D.14.7 D.14.7.1 D.14.7.2 D.14.7.3 D.14.7.4 D.14.7.5 D.14.7.5.1 D.14.7.6 D.14.7.7 D.14.7.7.1 D.14.7.7.2 D.14.7.7.3 D.14.7.7.4 D.14.8 D.14.8.1 D.14.8.2 D.14.8.2.1 May 17, 2012 Document 2 - Specification & Response Document Page 124 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.14 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.14.8.2.2 D.14.8.3 D.14.8.4 D.14.8.4.1 D.14.8.5 D.14.8.5.1 D.14.8.6 D.14.8.6.1 D.14.8.7 D.14.8.8 D.14.8.9 D.14.9 D.14.10 D.14.10.1 D.14.10.2 D.14.10.3 {End Section D.14} May 17, 2012 Document 2 - Specification & Response Document Page 125 of 399 Maricopa County, Arizona D.15 12030-RFP P25 Radio System Infrastructure Upgrade New Prefabricated Equipment Shelters Where practical and economical, new equipment shelters shall be prefabricated, constructed of precast steel-reinforced concrete, including floor and roof. D.15.1 Structural Requirements D.15.1.1 Floor Load The floor shall be designed per American Society of Civil Engineers standard 7-88 ("ASCE 7-88") Uniform Distributed Load of a minimum of 300 pounds per square foot. D.15.1.2 Roof Load The roof shall be designed per ASCE 7-88 based on a roof load specification of a minimum of 150 pounds per square foot. D.15.1.3 Wind Load Stresses and loads due to wind shall be calculated per ASCE 7-88 based on a Basic Wind Speed of 150 MPH. D.15.1.4 Other Stresses and Loads Design shall also account for stresses induced during handling, transportation and installation. D.15.1.5 Ballistic Rating Walls shall be rated Level 4 in accordance with Underwriters Laboratories standard UL-752. D.15.1.6 Foundation The building foundation shall be steel-reinforced concrete slab, installed in compliance with all applicable building codes. D.15.1.7 Concrete D.15.1.7.1 D.15.2 Roof D.15.2.1 May 17, 2012 Concrete shall have a 28-day minimum compressive strength of 5000 PSI. D.15.1.7.2 The concrete mix utilized shall be suitable for use in locations (the finished shelter's final destination) where ambient temperatures may vary between 0 deg. F and +125 deg. F. D.15.1.7.3 Cured concrete shall be sealed against water absorption and water intrusion. The roof shall be precast steel-reinforced concrete. D.15.2.2 The roof shall have at least a 1/8” per foot drainage slope and designed to prevent accumulation of water. D.15.2.3 The roof shall be a cap and fit over the walls, leaving no exposed roof to wall joints and shall provide a minimum 2” overhang on all sides. Document 2 - Specification & Response Document Page 126 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.14.2.4 Roof shall be securely bolted to adjoining walls. D.15.2.5 Roof shall be designed to prevent damage from falling ice. D.15.2.5.1 If required, a steel ice shield shall be installed to protect the roof from damage. D.15.3 Exterior Finish D.15.3.1 For shelters to be installed in unpopulated areas, finish shall be smooth concrete, colored to approximately match the surrounding environment. D.15.3.2 D.15.3.1.1 Concrete shall be dyed, not painted. D.15.3.1.2 Fins and other projections shall be completely removed and smoothed. For shelters to be installed in populated areas, shelters shall have an attractive aggregate finish, approximating the color of stones naturally found in Maricopa County. D.15.3.2.1 D.15.3.3 Aggregate finish shall be sealed against water absorption and intrusion. Certain locations shall require special finishes, as dictated by zoning or community standards. D.15.3.3.1 The Contractor shall be aware of these locations and shall inform the County in instances where a special finish is necessary. D.15.4 Interior Finish Interior shall be finished with 3/4 in. grade B-C sanded fire-retardant plywood (over insulation), primed and painted white. D.15.4.1 The Contractor may propose an alternate finish of similar or better quality. D.15.4.2 Drywall or other finishing material that does not provide a reliable medium for attachment of conduit or wall-mounted appurtenances shall not be acceptable. D.15.5 Other Requirements D.15.5.1 Openings for cable exit and entry, HVAC and other items shall be cast into the concrete rather than cut. May 17, 2012 D.15.5.2 Wall, floor and roof joints shall be sealed with an appropriate adhesive sealer that will not deteriorate or separate from the concrete under the environmental conditions found in Maricopa County. D.15.5.3 Shelters shall be insulated in accordance with applicable building codes. Document 2 - Specification & Response Document Page 127 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.15.5.4 Roof shall be insulated. D.15.5.5 Shelters shall be backed by a ten-year manufacturer's replacement warranty covering the structure, roof and installation. Document 2 - Specification & Response Document Page 128 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.15 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.15 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Standard Requirement Comply/ Section Exception D.15 D.15.1 D.15.1.1 D.15.1.2 D.15.1.3 D.15.1.4 D.15.1.5 D.15.1.6 D.15.1.7 D.15.1.7.1 D.15.1.7.2 D.15.1.7.3 D.15.2 D.15.2.1 D.15.2.2 D.15.2.3 D.15.2.4 D.15.2.5 D.15.2.5.1 D.15.3 D.15.3.1 D.15.3.1.1 D.15.3.1.2 D.15.3.2 D.15.3.2.1 D.15.3.3 D.15.3.3.1 D.15.4 D.15.4.1 D.15.4.2 D.15.5 D.15.5.1 May 17, 2012 Document 2 - Specification & Response Document Page 129 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.15 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Standard Standard Standard Standard Requirement Comply/ Section Exception D.15.5.2 D.15.5.3 D.15.5.4 D.15.5.5 {End Section D.15} May 17, 2012 Document 2 - Specification & Response Document Page 130 of 399 Maricopa County, Arizona D.16 12030-RFP P25 Radio System Infrastructure Upgrade Buildings Constructed On-Site Where prefabricated shelters cannot be utilized, masonry shelters shall be constructed on-site in accordance with Drawings A1 through A3 of Appendix 8. Final design of the structure shall be performed by the Contractor’s Architectural and Engineering subcontractor. D.16.1 Structural Requirements D.16.1.1 Floor Load The floor shall be designed per American Society of Civil Engineers standard 7-88 ("ASCE 7-88") Uniform Distributed Load of a minimum of 300 pounds per square foot. D.16.1.2 Roof Load The roof shall be designed per ASCE 7-88 based on a roof load specification of a minimum of 150 pounds per square foot. D.16.1.3 Wind Load Stresses and loads due to wind shall be calculated per ASCE 7-88 based on a Basic Wind Speed of 150 MPH. D.16.1.4 Foundation The building foundation shall be 2’-0” X 1’-0” concrete footing, installed in compliance with all applicable building codes. D.16.1.5 Concrete D.16.1.5.1 D.16.1.6 Footing concrete shall have a 28-day minimum compressive strength of 3000 psi and slump of 4”. D.16.1.5.2 The concrete mix utilized shall be suitable for use in locations where ambient temperatures may vary between 0 deg. F and +125 deg. F. D.16.1.5.3 Cured concrete shall be sealed against water absorption and intrusion. Masonry Walls D.16.1.6.1 Concrete Masonry Units (CMU) shall be 8” CMU that conform to ASTM C90, Type I, Grade N-1 normal weight. All CMU shall be filled with grout. May 17, 2012 D.16.1.6.2 #4 reinforcement rods shall extend through the top bond beam and be tied to horizontal reinforcement in bond beam at top, and footing dowels at the bottom. D.16.1.6.3 Grout shall conform to ASTM C476, Section 4 of ACI 530.1-88/ASCE 6-68. Minimum strength of grout shall be 2,000 psi. Document 2 - Specification & Response Document Page 131 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.16.1.6.4 D.16.2 Roof D.16.2.1 Mortar shall conform to ASTM C270, Type S. Mortar strength shall develop a minimum compressive strength of 1800 psi at 28 days. The roof supports shall be either pre-cast concrete planking or open web galvanized steel joists and galvanized steel deck. D.16.2.2 The roof shall have at least a 1/8” per foot drainage slope and designed to prevent accumulation of water. Tapered rigid roof insulation may be utilized to achieve desired sloping. D.16.2.3 Roof shall be designed to prevent damage from falling ice. D.16.2.3.1 If required, a steel ice shield shall be installed to protect the roof from damage. D.16.3 Exterior Finish D.16.3.1 For shelters to be installed in unpopulated areas the exterior CMU shall be sealed against moisture, primed, and painted a color that approximately matches the surrounding desert environment. D.16.3.2 For shelters to be installed in populated areas, pre-faced CMU shall be used. D.16.4 Interior Finish Interior shall be finished with 3/4 inch fire-retardant plywood (over rigid insulation), primed and painted white. D.16.5 Other Requirements D.16.5.1 Shelter construction shall have 2 hour fire rating. D.16.5.2 May 17, 2012 The shelter building envelope shall be watertight, dust-tight and fully weatherproofed. Document 2 - Specification & Response Document Page 132 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.16 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.16 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Standard Standard Requirement Comply/ Section Exception D.16 D.16.1 D.16.1.1 D.16.1.2 D.16.1.3 D.16.1.4 D.16.1.5 D.16.1.5.1 D.16.1.5.2 D.16.1.5.3 D.16.1.6 D.16.1.6.1 D.16.1.6.2 D.16.1.6.3 D.16.1.6.4 D.16.2 D.16.2.1 D.16.2.2 D.16.2.3 D.16.2.3.1 D.16.3 D.16.3.1 D.16.3.2 D.16.4 D.16.5 D.16.5.1 D.16.5.2 {End Section D.16} May 17, 2012 Document 2 - Specification & Response Document Page 133 of 399 Maricopa County, Arizona D.17 12030-RFP P25 Radio System Infrastructure Upgrade Requirements Common to All Equipment Spaces D.17.1 New Equipment Spaces The Contractor shall provide and construct new equipment spaces at new Sites that do not have an existing suitable space for equipment and at Sites with existing equipment spaces that do not meet and cannot be modified to meet the requirements of this Section D.17. D.17.2 Existing Equipment Spaces At sites with existing equipment spaces, the Contractor shall remodel the existing equipment space to meet the applicable requirements of this Section D.17. D.17.2.1 The equipment space shall be increased in size if required. D.17.2.2 Items required by this Section D.17 that are not present or inadequate in the existing equipment space (examples: grounding and lightning protection) shall be added or improved. D.17.2.3 At sites where the existing equipment space cannot be modified to meet the requirements of this Section D.17, the Contractor shall provide and construct a new equipment space. D.17.2.3.1 Upon completion of the new equipment space, the Contractor shall transfer all electronic equipment from the old equipment space to the new one. D.17.2.3.2 Upon completion of transfer of electronic equipment to the new equipment space, the Contractor shall dismantle and remove the old equipment space. Disposition of the old materials shall be at the discretion of the County. D.17.3 Size Equipment spaces shall be sized to house all Radio System equipment plus any equipment that is to be relocated from a previous equipment space. In addition, space shall be provided and reserved for two 19 inch EIA racks, each seven feet tall, to accommodate future growth. D.17.3.1 Optional Additional Future Growth Capacity At the County's discretion, the County may require the Contractor to provide and reserve space for a total of five 19 inch EIA racks, seven feet tall, to accommodate future growth instead of the two additional rack spaces specified in the above paragraph. D.17.4 Electrical Power Equipment spaces shall be completely wired for electrical power by the Contractor. May 17, 2012 D.17.4.1 Electrical wiring shall comply with NEC and local codes and regulations. D.17.4.2 AC power wiring shall be installed in EMT conduit. Document 2 - Specification & Response Document Page 134 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.17.4.3 Two twenty-Ampere duplex outlets shall be mounted along the overhead cable ladder at the top of each equipment rack (or future rack space). D.17.4.4 Twenty-Ampere duplex outlets shall be placed at four foot intervals on each of the four interior walls. D.17.4.5 Each outlet shall be served by a separate circuit. D.17.4.6 An outdoor twenty-Ampere GFCI duplex outlet supported by the generator shall be provided near the entry door. D.17.4.7 All electrical outlets shall be backed up by the generator. D.17.4.8 Certain outlets may be required to be backed up by a UPS. These outlets shall be identified by an orange color. D.17.4.9 Each outlet shall be permanently labeled with its associated electrical panel and circuit breaker. D.17.4.9.1 D.17.4.10 Hand written labels shall not be acceptable. Transient Voltage Suppression Systems (TVSS) shall be provided to protect the AC main panel and critical sub panels. D.17.5 Floors Floors shall be covered with antistatic vinyl tile, light gray in color. The tile shall have the following characteristics: D.17.5.1 Minimum thickness shall be 0.125 in. D.17.5.2 Static load of minimum 2,500 PSI when tested according to ASTM F-97000 D.17.5.3 Flame spread <75 when tested according to ASTM E-84 and NFPA-225. D.17.5.4 Smoke density <450 when tested according to ASTM E-662. D.17.5.5 Resistance of between 25,000 Ohms and 2.5 MegOhms when tested under conditions specified in ESD-7.1 and ASTM F-150 at 30 percent relative humidity. D.17.5.6 Resistant to oil, grease, acids, alkalis and solvents. D.17.5.7 Ten-year ESD warranty. D.17.5.8 Floor covering shall be installed in compliance with the floor covering manufacturer's recommendations. D.17.6 Interior Lighting D.17.6.1 Interior lighting shall provide a level of 75 foot-candles at 3 feet above the floor. May 17, 2012 Document 2 - Specification & Response Document Page 135 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.17.6.2 Interior light shall be provided by fluorescent fixtures using two standard four foot tubes per fixture. D.17.6.3 Light fixtures shall be installed to the front and rear of electronic equipment racks to prevent racks and equipment from casting shadows. D.17.6.4 Interior lights shall be controlled by a timer that will automatically turn the lights off if not reset within a two-hour period. D.17.6.5 The control for the interior lights shall be located inside, adjacent to and on the latch side of the entry door. D.17.7 Exterior Lighting D.17.7.1 Exterior lighting shall be provided adjacent to the entry door to the equipment shelter/equipment space in a manner to avoid shading by the open door and awning. D.17.7.2 Exterior lighting shall be controlled by a motion sensor that shall turn on the exterior lights whenever a human being or a vehicle is within twenty feet of the entry door. D.17.7.3 The sensitivity of the motion sensor shall be set to minimize undesired activation by small animals or birds. D.17.7.4 Exterior lighting fixtures and motion sensors shall be heavy duty, shatterproof and tamper resistant. D.17.8 Exterior Doors D.17.8.1 Exterior doors shall be heavy duty, fully welded steel door and framing, primed and painted, tamper-proof hinges, three point latch, fiberglass cap and solid grouted jamb. D.17.8.2 Exterior doors shall be a minimum of 48 inches wide and 84 inches high. D.17.8.3 Exterior doors shall be ballistic-rated Level 4 in accordance with Underwriters Laboratories standard UL-752. D.17.8.4 Exterior doors shall have a minimum two hour fire rating. D.17.8.5 Exterior doors shall be weatherstripped and sealed against entry by insects, vermin, dust, smoke and moisture. D.17.8.6 Exterior doors shall have an anti-pick plate on strike of door to prevent access to the latch and deadbolt. D.17.8.7 A drip awning shall be installed over each door to prevent water entry into the building. D.17.9 HVAC Air conditioning and heating shall be provided. May 17, 2012 Document 2 - Specification & Response Document Page 136 of 399 Maricopa County, Arizona D.17.9.1 12030-RFP P25 Radio System Infrastructure Upgrade The interior temperature of the equipment space shall be maintained between 65 and 85 degrees Fahrenheit when outside temperatures are between 0 and +120 degrees Fahrenheit. D.17.9.1.1 Equipment spaces shall be insulated as necessary to meet the temperature requirement. D.17.9.2 Relative humidity shall be maintained at a level acceptable to the equipment to be installed in the equipment space. D.17.9.3 There shall be a minimum of two air conditioning units installed with a standard lead/lag switch arrangement set to cycle between the units. D.17.9.4 HVAC units shall be sized for a 30% future growth in power dissipation of equipment installed inside the equipment space. D.17.9.5 HVAC units shall have the highest possible cooling efficiency rating, minimum EER of 10.0. D.17.9.6 HVAC units shall be through-wall mounted unless wall mounting is impractical. D.17.9.6.1 HVAC units shall not be roof-mounted unless that is the only option. D.17.9.7 At sites where snow accumulation may occur, HVAC units shall be installed so that accumulated snow does not block air flow around the units. D.17.9.8 HVAC units shall be designed to prevent entry by insects, vermin, dust, smoke and moisture. D.17.9.9 Exterior compressors, blowers and other moving or vibrating parts shall be insulated to muffle noise. D.17.10 Transmission Line Entry Port A transmission line entry port with modular feed through plates shall be installed in the wall of the equipment space adjacent to the antenna support structure. May 17, 2012 D.17.10.1 The transmission line entry port shall be installed in horizontal and vertical alignment with interior cable ladders arranged over the equipment rack space. D.17.10.2 The transmission line entry port shall be a modular design, have a 1 hour fire rating for floor and wall penetrations, be water and gas pressure rated up to 4 bars. D.17.10.3 The transmission line entry port shall be designed to stop flames from a burning transmission line jacket from entering the equipment space. Document 2 - Specification & Response Document Page 137 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.17.10.3.1 The transmission line entry port shall be Roxtec GFrame stainless steel multi-diameter cable entry system or approved equal. D.17.10.4 Sufficient entry ports shall be provided to support the Radio System and all other antennas and transmission lines specified in Sections D.14.6.2 and D.14.6.3 (including optional capacity), above. D.17.10.5 All unused entry ports shall be sealed with removable firestop seals. D.17.11 Interior Cable Ladder A cable ladder shall be installed over all equipment rack spaces, and to the telephone equipment panel, and to any future equipment expansion space in the equipment shelter/space. D.17.11.1 Width of the interior cable ladder shall be sufficient to accommodate all cabling required by new and existing equipment, plus an additional 50 percent for future growth. D.17.11.1.1 Cable ladders shall be sized to meet the minimum cable spacing and other requirements stated in Section D.2.3. D.17.11.1.2 Minimum width shall be 12 inches. D.17.11.2 Interior cable ladders shall be constructed of metal. D.17.11.3 Interior cable ladders shall be bonded and grounded in compliance with Appendix 5 – Grounding and Lightning Suppression Requirements. D.17.12 Fire Protection System The contractor shall provide and install an automatic fire protection system in all equipment shelters and equipment spaces. D.17.12.1 The fire protection system shall consist of: D.17.12.1.1 May 17, 2012 An automatic fire alarm system that, when excessive heat is detected: D.17.12.1.1.1 Activates a local audible and visual alarm. D.17.12.1.1.2 Reports the detection of fire to the building's main fire alarm panel and other locations as required by applicable fire codes. D.17.12.1.1.3 Reports the detection of fire to other locations as may be required by the building owner or the County. Document 2 - Specification & Response Document Page 138 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.17.12.1.2 An automatic fire suppression system, activated upon detection of excessive heat that will extinguish the fire while causing minimal damage to electronic equipment. D.17.12.2 A means to manually activate the fire protection system shall be provided in each shelter/space. D.17.12.3 The automatic fire protection system shall comply with all applicable fire codes, building codes and safety laws and regulations. D.17.13 Grounding and Lightning Suppression Grounding, both interior and exterior, shall comply with the requirements of Appendix 5. May 17, 2012 Document 2 - Specification & Response Document Page 139 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.17 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.17 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.17 D.17.1 D.17.2 D.17.2.1 D.17.2.2 D.17.2.3 D.17.2.3.1 D.17.2.3.2 D.17.3 D.17.3.1 D.17.4 D.17.4.1 D.17.4.2 D.17.4.3 D.17.4.4 D.17.4.5 D.17.4.6 D.17.4.7 D.17.4.8 D.17.4.9 D.17.4.9.1 D.17.4.10 D.17.5 D.17.5.1 D.17.5.2 D.17.5.3 D.17.5.4 D.17.5.5 D.17.5.6 D.17.5.7 D.17.5.8 D.17.6 May 17, 2012 Document 2 - Specification & Response Document Page 140 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.17 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.17.6.1 D.17.6.2 D.17.6.3 D.17.6.4 D.17.6.5 D.17.7 D.17.7.1 D.17.7.2 D.17.7.3 D.17.7.4 D.17.8 D.17.8.1 D.17.8.2 D.17.8.3 D.17.8.4 D.17.8.5 D.17.8.6 D.17.8.7 D.17.9 D.17.9.1 D.17.9.1.1 D.17.9.2 D.17.9.3 D.17.9.4 D.17.9.5 D.17.9.6 D.17.9.6.1 D.17.9.7 D.17.9.8 D.17.9.9 D.17.10 D.17.10.1 D.17.10.2 May 17, 2012 Document 2 - Specification & Response Document Page 141 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.17 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.17.10.3 D.17.10.3.1 D.17.10.4 D.17.10.5 D.17.11 D.17.11.1 D.17.11.1.1 D.17.11.1.2 D.17.11.2 D.17.11.3 D.17.12 D.17.12.1 D.17.12.1.1 D.17.12.1.1.1 D.17.12.1.1.2 D.17.12.1.1.3 D.17.12.1.2 D.17.12.2 D.17.12.3 D.17.13 {End Section D.17} May 17, 2012 Document 2 - Specification & Response Document Page 142 of 399 Maricopa County, Arizona D.18 12030-RFP P25 Radio System Infrastructure Upgrade Site Physical Security D.18.1 Fencing Unless otherwise directed by the County, all sites shall be fenced. D.18.1.1 All sites that are not currently fenced shall receive a new fence that conforms to the requirements of this Section. If a site has an existing fence that does not meet the requirements of this Section, the fence shall be repaired and upgraded to meet the requirements of this Section. D.18.1.2 Fence Specifications Fences shall: D.18.1.2.1 Be chain-link type unless otherwise directed by the County; D.18.1.2.1.1 May 17, 2012 Other types of fencing may be required depending on local zoning and community standards. D.18.1.2.2 Be constructed of completely hot-dipped galvanized steel; D.18.1.2.3 Have posts of nominal 4 inch Schedule 80 pipe D.18.1.2.3.1 Posts shall be capped to prevent moisture accumulation inside the pipe D.18.1.2.3.2 Posts shall be set in concrete at a sufficient depth to prevent shifting if struck by a moving vehicle D.18.1.2.3.3 Posts shall be evenly spaced at no greater than ten foot intervals D.18.1.2.3.4 End, corner, pull and gateposts are to be braced with the same material as top and bottom rail D.18.1.2.3.5 Posts shall be aligned and installed plumb D.18.1.2.4 Have a fabric height of eight (8) feet (excluding barbed wire) using 2 inch mesh / 9 gauge (minimum) fabric with zinc coating; D.18.1.2.5 Have both a top and a bottom rail using nominal 1-1/4” Schedule 80 pipe; Document 2 - Specification & Response Document Page 143 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.18.1.2.6 Be topped with three strands of class 3 galvanized barbed wire on extension arms extending upward and outward at a 45-degree angle; D.18.1.2.7 Have a double swing gate, twelve feet wide to permit entry of vehicles onto the site D.18.1.2.8 D.18.1.2.9 D.18.1.2.7.1 The gate shall be braced to prevent drooping and deformation D.18.1.2.7.2 The gate shall be positioned to provide easy access to the front door of the equipment shelter D.18.1.2.7.3 The gate shall include a positive type latching device with provisions for padlocking Have a man gate, minimum 36 inches wide, positioned for easy access for re-filling the generator fuel tank if the placement of the fuel tank makes access from the double swing gate inconvenient. D.18.1.2.8.1 The gate shall be braced to prevent drooping and deformation D.18.1.2.8.2 The gate shall include a positive type latching device with provisions for padlocking For guyed towers, all guy anchors must have a perimeter security fence installed that meets the requirements of this Section with a minimum clearance between the fence and guy anchor or guy wire of at least three feet. D.18.1.2.9.1 May 17, 2012 A man gate, minimum 36 inches wide, shall be provided at each guy anchor location to allow access to guy anchor. D.18.1.2.10 Fences at all sites, new and existing, shall be grounded in accordance with Appendix 5 - Grounding and Lightning Suppression Requirements D.18.1.2.11 Fence and gate connecting devices shall be made of non-corrosive materials and installed to prevent loosening due to vibration. Document 2 - Specification & Response Document Page 144 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.18.1.2.12 The Contractor shall ensure that the grade at the fence line is correct and final before the fence is installed. D.18.1.2.13 Installation work shall be performed by experienced fence erectors. D.18.2 Access Road Gates Where new access roads are to be constructed (and at other access roads as may be directed by the County) the access road shall have a gate placed across it to prevent access by unauthorized vehicles. D.18.2.1 A gate of the appropriate width, but no narrower than the width necessary to allow construction equipment to pass when necessary, shall be installed at the point where the access road meets the first public road (or other location which may be specified by the County). D.18.2.2 The gate shall be constructed of no less than 4 inch schedule 80 galvanized steel pipe. D.18.2.3 The gate shall be of welded construction. D.18.2.4 The gate shall be primed and painted a medium brown color which is visible against its background yet approximates the colors of the surrounding environment. D.18.2.5 The gate shall have a minimum of four, four-inch reflectors on both sides for visibility at night. D.18.2.5.1 D.18.2.6 A sign shall be installed upon the gate stating "Authorized Vehicles Only" and the telephone number of the OET Wireless Systems shop for persons to request access. D.18.2.7 Bollards shall be placed alongside the gate if necessary to prevent vehicles from going around the gate. D.18.2.8 Gateposts and bollards shall be filled with concrete. D.18.2.9 Gateposts and bollards shall be capped to prevent moisture accumulation. D.18.2.10 The gate shall be equipped with a multiple-padlocking device that permits no less than five padlocks to secure the gate in a manner whereby removal of any individual padlock will allow the gate to be opened without the removal of any other padlock. D.18.2.10.1 May 17, 2012 Reflectors shall be screwed or bolted in place. Attachment using adhesives only is not acceptable. Padlocks shall be shielded by steel plates to prevent damage to the padlocks from bullets. Document 2 - Specification & Response Document Page 145 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.18.3 Padlocks The Contractor shall provide one heavy-duty padlock (with two keys each) for every fence gate, one padlock for every electrical box (where required by Section D.10.1.2) and five heavy-duty padlocks (with two keys each) for each access road gate. D.18.3.1 Padlocks shall not be combination-type locks. D.18.3.2 Padlocks shall be keyed as directed by the County. D.18.4 Americans with Disabilities Act Compliance All Sites shall comply with applicable provisions of the Americans With Disabilities Act ("ADA"). May 17, 2012 Document 2 - Specification & Response Document Page 146 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.18 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.18 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.18 D.18.1 D.18.1.1 D.18.1.2 D.18.1.2.1 D.18.1.2.1.1 D.18.1.2.2 D.18.1.2.3 D.18.1.2.3.1 D.18.1.2.3.2 D.18.1.2.3.3 D.18.1.2.3.4 D.18.1.2.3.5 D.18.1.2.4 D.18.1.2.5 D.18.1.2.6 D.18.1.2.7 D.18.1.2.7.1 D.18.1.2.7.2 D.18.1.2.7.3 D.18.1.2.8 D.18.1.2.8.1 D.18.1.2.8.2 D.18.1.2.9 D.18.1.2.9.1 D.18.1.2.10 D.18.1.2.11 D.18.1.2.12 D.18.1.2.13 D.18.2 D.18.2.1 D.18.2.2 May 17, 2012 Document 2 - Specification & Response Document Page 147 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.18 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.18.2.3 D.18.2.4 D.18.2.5 D.18.2.5.1 D.18.2.6 D.18.2.7 D.18.2.8 D.18.2.9 D.18.2.10 D.18.2.10.1 D.18.3 D.18.3.1 D.18.3.2 D.18.4 {End Section D.18} May 17, 2012 Document 2 - Specification & Response Document Page 148 of 399 Maricopa County, Arizona D.19 12030-RFP P25 Radio System Infrastructure Upgrade Misc. Site Amenities D.19.1 A concrete walkway shall be installed between the shelter entry door, the antenna support structure and the gate to the fence surrounding the Site to facilitate access by persons with disabilities and to allow equipment to be easily brought into the shelter on hand trucks without tracking dirt into the building. D.19.2 A cable bridge and ice shield shall be provided between the equipment shelter or equipment space transmission line entry port and the antenna support structure cable ladder to prevent damage to transmission lines from ice and other objects falling from the antenna support structure. D.19.2.1 Galvanized steel construction shall be used for the cable bridge and its ancillary components. D.19.2.2 The cable bridge shall be supported by a minimum of two galvanized steel posts of sufficient strength to prevent deformation when subjected to winds of 90 MPH. D.19.2.3 The cable bridge shall not be mechanically or electrically connected to either the antenna support structure or the equipment shelter/equipment space. D.19.2.4 Provisions shall be made to install cables neatly and in a manner where an individual cable may be removed without disturbing the others. D.19.2.5 Cable bridges at all sites, new and existing, shall be grounded in accordance with Appendix 5 - Grounding and Lightning Suppression Requirements. D.19.2.6 The height of the cable bridge shall match the height of the cable entry port on the equipment shelter or equipment space. D.19.3 For all sites, warning and informational signs shall be furnished and installed in appropriate locations at each site. Signs shall include but not be limited to: May 17, 2012 D.19.3.1 FCC ASR number D.19.3.2 A sign designating the telephone number(s) to be dialed for site access and in an emergency D.19.3.3 "No Trespassing” D.19.3.4 RF exposure hazard warning(s) D.19.3.5 A sign attached to each leg of towers and other antenna support structures reading "DANGER - DO NOT CLIMB" or similar wording. Document 2 - Specification & Response Document Page 149 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.19.4 Protection From Falling Ice At Sites at elevations above 3,000 feet AMSL, ice shields constructed of steel grating shall be installed to protect outdoor equipment that may be damaged from ice falling from the tower. May 17, 2012 Document 2 - Specification & Response Document Page 150 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.19 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section D.19 D.19.1 D.19.2 D.19.2.1 D.19.2.2 D.19.2.3 D.19.2.4 D.19.2.5 D.19.2.6 D.19.3 D.19.3.1 D.19.3.2 D.19.3.3 D.19.3.4 D.19.3.5 D.19.4 12030-RFP, Document 2, Section D.19 Comply/ Exception Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard {End Section D.19} May 17, 2012 Document 2 - Specification & Response Document Page 151 of 399 Maricopa County, Arizona D.20 12030-RFP P25 Radio System Infrastructure Upgrade Trunked/LMR Subsystem RF Coverage Requirements D.20.1 Limiting Case The extent to which the Contractor's/Respondent's proposed solution complies with the RF coverage requirements of this RFP shall be determined by the limiting case, either talk-out (repeater transmitting to portable radio in the field) or talk-back (portable radio in the field transmitting to the repeater), whichever is least. D.20.2 Definitions D.20.2.1 Delivered Audio Quality The definition of Delivered Audio Quality ("DAQ") shall be the definition used in the latest revision of TIA/EIA Telecommunications Systems Bulletin TSB88, "Wireless Communications Systems - Performance In Noise and Interference-Limited Situations - Recommended Methods For Technology-Independent Modeling, Simulation, and Verification.” D.20.2.2 Portable Coverage "Portable Coverage" shall be defined as a minimum DAQ of 3.4, at a minimum reliability at any given location of ninety-five percent (95%), while using a portable radio with a half-wave coaxial dipole antenna, outdoors, worn on the hip using a belt clip or belt-loop case and used with a remote speaker-microphone. Antenna is located on the portable radio, not on the speaker-microphone. A vehicular repeater is not used. D.20.2.3 Greater Phoenix Area and Other Defined Areas The Greater Phoenix Area and other areas with special radio coverage requirements are defined in Appendix 1. Shape files of these defined areas in Arc View format and referenced to latitude and longitude are included in the Zip file that may be downloaded from the Maricopa County Office of Procurement Services web site, https://www.bidsync.com/. See Appendix 4. D.20.3 Required Radio Coverage D.20.3.1 "Basic Coverage Requirement": The Contractor's solution shall provide Portable Coverage over a minimum of eighty percent (80%) of the entire geographic area of Maricopa County. D.20.3.2 The Contractor's solution shall also meet the following requirements for specific roads and locations. If the road or location specified lies within Maricopa County, it shall count toward fulfillment of the Basic Coverage Requirement. Roads and locations or portions of roads and locations lying outside of Maricopa County shall not count toward fulfillment of the Basic Coverage Requirement. D.20.3.2.1 May 17, 2012 All Interstate highways, National highways, State highways except for Arizona Highway 88, and numbered County roads shall have a minimum of Portable Document 2 - Specification & Response Document Page 152 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Coverage over a minimum of ninety-five percent (95%) of their length within Maricopa County. May 17, 2012 D.20.3.2.2 Arizona Highway 88 shall have a minimum of Portable Coverage over a minimum of fifty percent (50%) of its length within Maricopa County. D.20.3.2.3 Additional roads that each shall have a minimum of Portable Coverage over a minimum of eighty-five percent (85%) of their length within Maricopa County, or, if the road lies outside Maricopa County, eighty-five percent (85%) of the portion of the road specified: D.20.3.2.3.1 Eagle Eye Road D.20.3.2.3.2 Aguila Road D.20.3.2.3.3 Wickenburg Road D.20.3.2.3.4 Vulture Mine Road D.20.3.2.3.5 Sun Valley Parkway D.20.3.2.3.6 Old U.S. 80 D.20.3.2.3.7 Agua Caliente-Arlington Road D.20.3.2.3.8 Southern Pacific Trail (Union Pacific Railroad Right-of-Way between Arlington and Hyder) D.20.3.2.3.9 New River Road D.20.3.2.3.10 Cave Creek Road D.20.3.2.3.11 West Riggs Road D.20.3.2.3.12 Beltline Road D.20.3.2.3.13 Arizona Highway 238 in Pinal County from the Maricopa County border to the junction of Arizona Highway 347. D.20.3.2.3.14 Arizona Highway 347 in Pinal County from the Maricopa County border to the junction of Arizona Highway 238. D.20.3.2.3.15 Interstate 8 in Pinal County from the Maricopa County border to the junction of Interstate 10. Document 2 - Specification & Response Document Page 153 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.20.3.2.4 D.20.3.2.5 May 17, 2012 The following County parks shall have a minimum of Portable Coverage over a minimum of seventy-five percent (75%) of their defined areas: D.20.3.2.4.1 Lake Pleasant Regional Park (including portions in Yavapai County) D.20.3.2.4.2 San Tan Mountain Regional Park (in Pinal County) D.20.3.2.4.3 McDowell Mountain Regional Park D.20.3.2.4.4 Usery Mountain Regional Park D.20.3.2.4.5 White Tanks Mountain Regional Park The following lakes and reservoirs shall have a minimum of Portable Coverage over a minimum of eighty percent (80%) of their defined areas: D.20.3.2.5.1 Horseshoe Reservoir (including portions in Yavapai County) D.20.3.2.5.2 Bartlett Reservoir D.20.3.2.5.3 Saguaro Lake D.20.3.2.5.4 Canyon Lake D.20.3.2.5.5 Apache Lake (including portions in Gila County) D.20.3.2.5.6 Theodore Roosevelt Lake (in Gila County) D.20.3.2.6 The area within a ten mile radius of 33-23-14.0 N latitude, 112-51-55.0 W longitude (the location of the Palo Verde Nuclear Generating Station) shall have a minimum of Portable Coverage over a minimum of eighty-five percent (85%) of the area. D.20.3.2.7 The area defined as the Vekol Valley shall have a minimum of Portable Coverage over a minimum of eighty percent (80%) of its defined area. D.20.3.2.8 The area defined as Paradise Valley shall have a minimum of Portable Coverage over a minimum of ninety percent (90%) of its defined area. Document 2 - Specification & Response Document Page 154 of 399 Maricopa County, Arizona D.20.3.3 12030-RFP P25 Radio System Infrastructure Upgrade Areas requiring additional signal strength margins for building penetration: The areas described below shall be provided with additional signal strength above that required to provide Portable Coverage. If the area specified lies within Maricopa County, it shall count toward fulfillment of the Basic Coverage Requirement. Areas or portions of areas lying outside of Maricopa County shall not count toward fulfillment of the Basic Coverage Requirement. Defined areas may overlap. D.20.3.3.1 D.20.3.3.2 D.20.3.3.3 For the area defined as the Greater Phoenix Area, the Contractor's solution shall provide: D.20.3.3.1.1 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of seventyfive percent (75%) of the defined area, and D.20.3.3.1.2 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetyfive percent (95%) of the defined area. For the area defined as Government Center, the Contractor's solution shall provide: D.20.3.3.2.1 At least 18 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of eightyfive percent (85%) of the defined area, and D.20.3.3.2.2 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetynine percent (99%) of the defined area. For the area defined as Urban Center North, the Contractor's solution shall provide: D.20.3.3.3.1 May 17, 2012 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of eightyfive percent (85%) of the defined area, and, Document 2 - Specification & Response Document Page 155 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.20.3.3.3.2 D.20.3.3.4 D.20.3.3.5 D.20.3.3.6 May 17, 2012 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetynine percent (99%) of the defined area. For the area defined as Queen Creek, including the portions in Pinal County, the Contractor's solution shall provide: D.20.3.3.4.1 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of eightyfive percent (85%) of the defined area, and D.20.3.3.4.2 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetyeight percent (98%) of the defined area. For the area defined as Gila Bend, the Contractor's solution shall provide: D.20.3.3.5.1 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetyfive percent (95%) of the defined area, and D.20.3.3.5.2 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetynine percent (99%) of the defined area. For the area defined as Wickenburg, the Contractor's solution shall provide: D.20.3.3.6.1 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of seventy percent (70%) of the defined area, and D.20.3.3.6.2 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninety percent (90%) of the defined area. Document 2 - Specification & Response Document Page 156 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.20.3.3.7 D.20.3.3.8 For the area defined as Fountain Hills, the Contractor's solution shall provide: D.20.3.3.7.1 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of eighty percent (80%) of the defined area, and D.20.3.3.7.2 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of ninetyfive percent (95%) of the defined area. For the area defined as Cave Creek, the Contractor's solution shall provide: D.20.3.3.8.1 At least 12 dBm greater than the signal strength required to provide Portable Coverage, over fifty percent (50%) of the defined area, and D.20.3.3.8.2 At least 6 dBm greater than the signal strength required to provide Portable Coverage, over a minimum of seventyfive percent (75%) of the defined area. D.20.3.3.8.3 Portable Coverage over a minimum of ninety-five percent (95%) of the defined area. D.20.4 Balanced Talk-Out and Talk-Back Coverage Coverage for talk-out (repeater transmitting to a portable radio in the field) and talkback (portable radio in the field transmitting to the repeater) shall be approximately equal. In particular, portable talk-out coverage shall not significantly exceed portable talk-back coverage. This is required to prevent the Radio System from giving users a false sense of security that they are in a good coverage area when they are actually in an area where they cannot talk back. D.20.5 Coverage Inside Buildings D.20.5.1 The County expects that its in-building coverage needs will be met by the requirement for additional signal strength margins in the areas specified above. D.20.5.2 May 17, 2012 Certain County buildings, including jails and courts, have Bi-Directional Amplifiers ("BDAs") that were previously installed and work with the existing 800 MHz trunked radio system. Requirements for upgrading the Document 2 - Specification & Response Document Page 157 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade existing BDA installations for use with the new Radio System infrastructure will be included in Section D.21.17 of this document. D.20.6 Radio Frequency Noise and Interference at Antenna Sites RF noise and interference at each site shall be taken into account in the Contractor's coverage design. May 17, 2012 Document 2 - Specification & Response Document Page 158 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.20 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.20 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.20 D.20.1 D.20.2 D.20.2.1 D.20.2.2 D.20.2.3 D.20.3 D.20.3.1 D.20.3.2 D.20.3.2.1 D.20.3.2.2 D.20.3.2.3 D.20.3.2.3.1 D.20.3.2.3.2 D.20.3.2.3.3 D.20.3.2.3.4 D.20.3.2.3.5 D.20.3.2.3.6 D.20.3.2.3.7 D.20.3.2.3.8 D.20.3.2.3.9 D.20.3.2.3.10 D.20.3.2.3.11 D.20.3.2.3.12 D.20.3.2.3.13 D.20.3.2.3.14 D.20.3.2.3.15 D.20.3.2.4 D.20.3.2.4.1 D.20.3.2.4.2 D.20.3.2.4.3 D.20.3.2.4.4 May 17, 2012 Document 2 - Specification & Response Document Page 159 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.20 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.20.3.2.4.5 D.20.3.2.5 D.20.3.2.5.1 D.20.3.2.5.2 D.20.3.2.5.3 D.20.3.2.5.4 D.20.3.2.5.5 D.20.3.2.5.6 D.20.3.2.6 D.20.3.2.7 D.20.3.2.8 D.20.3.3 D.20.3.3.1 D.20.3.3.1.1 D.20.3.3.1.2 D.20.3.3.2 D.20.3.3.2.1 D.20.3.3.2.2 D.20.3.3.3 D.20.3.3.3.1 D.20.3.3.3.2 D.20.3.3.4 D.20.3.3.4.1 D.20.3.3.4.2 D.20.3.3.5 D.20.3.3.5.1 D.20.3.3.5.2 D.20.3.3.6 D.20.3.3.6.1 D.20.3.3.6.2 D.20.3.3.7 D.20.3.3.7.1 D.20.3.3.7.2 May 17, 2012 Document 2 - Specification & Response Document Page 160 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.20 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Requirement Comply/ Section Exception D.20.3.3.8 D.20.3.3.8.1 D.20.3.3.8.2 D.20.3.3.8.3 D.20.4 D.20.5 D.20.5.1 D.20.5.2 D.20.6 {End Section D.20} May 17, 2012 Document 2 - Specification & Response Document Page 161 of 399 Maricopa County, Arizona D.21 12030-RFP P25 Radio System Infrastructure Upgrade Trunked/LMR Subsystem Functional and Technical Requirements D.21.1 700 MHz The Radio System shall utilize the 700 MHz public safety frequency band. If there are not a sufficient number of frequencies available for the entire Radio System to utilize 700 MHz, the 800 MHz band may also be used. D.21.2 Project 25 Phase 2 The Radio System shall be implemented utilizing Project 25 Phase 2 (TDMA) technology with backward compatibility with subscriber radios that are only capable of Phase 1 (FDMA). D.21.2.1 Normal mode of operation shall be Phase 2 TDMA. D.21.2.2 Whenever one or more Phase 1-only subscribers affiliate to a talkgroup, that talkgroup will immediately revert to Phase 1 FDMA without manual intervention by the user or system administrator. D.21.2.3 All repeaters at all sites shall be automatically backward-compatible with Project 25 Phase 1 (FDMA). D.21.3 Trunking The Radio System shall be trunked and shall comply with all applicable Project 25 standards for trunked radio systems. D.21.4 Traffic Capacity D.21.4.1 The Radio System shall be designed for a 0.01 Grade of Service ("GoS") when supporting the traffic load carried by the existing system plus additional spare capacity to support future growth of the subscriber fleet. An additional amount is also required to account for increases in traffic and decreases in capacity when Phase 1-only subscribers roam onto the County radio system for interoperability purposes. D.21.4.2 Traffic information from the County's existing trunked system may be found in Document 3 - Confidential Supplement. D.21.4.3 In addition to the current traffic load, the Radio System shall have sufficient capacity to support 30 percent future growth in the subscriber radio fleet (all law enforcement users). D.21.4.4 In addition to the above, every simulcast cell and multicast site (excluding Micro-Sites, if deployed) shall have sufficient capacity to support an interoperable, multi-jurisdictional, multi-discipline incident where numerous users with Phase 1 only subscriber radios are on-scene and communicating through the County's radio system. For calculation of traffic capacity, it shall be assumed that: D.21.4.4.1 May 17, 2012 The incident will operate on five heavily used Phase 1 FDMA talkgroups. Document 2 - Specification & Response Document Page 162 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.4.4.2 Radio system traffic other than the incident traffic shall be only minimally impacted. D.21.5 Wide-Area Operation D.21.5.1 Seamless Roaming Subscriber Radios shall be equipped to seamlessly roam throughout the coverage area without user intervention. Radios shall automatically affiliate and de-affiliate with Antenna Sites as needed to obtain the best coverage. D.21.5.2 Simulcast Transmitters The Contractor shall design its solution to maximize simulcast coverage and minimize the use of multicast. Simulcast "cells" shall be as large as possible to minimize problems associated with subscriber roaming. D.21.5.3 Receiver Comparators Receiver comparators shall be provided as needed to provide wide-area talk-back coverage. D.21.5.4 Auxiliary Receivers Auxiliary receivers may be used to augment talk-back coverage. D.21.6 Trunked Feature Set D.21.6.1 Transmitting Unit Identification The Radio System shall identify each Subscriber Radio with a unique identification (“PTT ID”) which is transmitted by the Subscriber Radio upon every PTT. The PTT ID shall be displayed in real time at dispatch consoles, system administration and maintenance consoles and other devices as required. D.21.6.2 May 17, 2012 D.21.6.1.1 The Radio System shall maintain a table of aliases for each PTT ID. The PTT ID shall normally be displayed as an alphanumeric alias rather than in native format. For example, the PTT ID of the radio assigned to the vehicle TRAFFIC 4 would be displayed as “TRAFFIC 4” instead of an electronic serial number or other coded format. D.21.6.1.2 Any character defined in the table of ASCII characters shall be utilized in an alias. D.21.6.1.3 Aliases shall consist of from one to sixteen characters. Signaling (Control) Channel The control channel shall continually transmit the current channel assignments of the system in order to ensure that radios "signing on", coming into range, or switching talkgroup modes are directed to calls in progress on their selected talkgroup. Document 2 - Specification & Response Document Page 163 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.6.2.1 D.21.6.3 Emergency Alarm Functionality Upon activation of an emergency switch on the subscriber radio unit, that subscriber unit and its associated talkgroup will be immediately put into "emergency" status. D.21.6.3.1 A talkpath shall be exclusively assigned to the emergency talkgroup until the emergency status is cleared by the originating subscriber unit or the dispatcher. D.21.6.3.2 The “emergency unit” itself and all subscriber radios monitoring that talkgroup shall display an indication that an emergency call is in progress. D.21.6.3.3 In the event all voice channels are occupied, the system shall be equipped to function in at least the following two (2) modes: D.21.6.3.4 D.21.6.4 May 17, 2012 Embedded signaling shall be transmitted over voice talkpaths in order to prevent subscribers from being misdirected or allowed to transmit on an improperly assigned channel. D.21.6.3.3.1 Emergency Priority Queuing. The unit initiating the emergency shall be placed at the top of the busy queue list. D.21.6.3.3.2 Emergency Pre-Emption. The unit initiating the emergency shall be immediately granted access to the voice channel with the lowest priority user currently assigned. The lower-priority call is terminated. The System Administrator shall have the capability to select either of the two modes on a talkgroup-bytalkgroup basis. Individual Unit Alert Dispatchers and certain subscriber radios shall be equipped to send an alert to individual subscriber radios. D.21.6.4.1 The subscriber radio receiving the alert shall emit an audible and visual alarm. D.21.6.4.2 The alarm shall automatically cancel after a predetermined length of time. Document 2 - Specification & Response Document Page 164 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.6.4.3 D.21.6.5 D.21.6.6 Individual Call Dispatchers and selected subscriber radio units shall have the ability to selectively communicate “privately” with another subscriber radio regardless of current talkgroup affiliation. D.21.6.5.1 The participating subscriber radios shall utilize a single channel resource to communicate with each other without the participation of other subscriber radios in their respective talkgroups. D.21.6.5.2 If the recipient of an individual call has a display-type radio, the radio shall display the PTT ID alias of the calling party, if one is defined. Otherwise, the PTT ID shall be displayed. D.21.6.5.3 The calling party shall be able to determine if the recipient did not receive the call or is not available for the call (i.e. recipient’s radio is turned off, out of range, etc.) through a distinctive tone and a text message in their display (if so equipped). D.21.6.5.4 All subscriber radios shall be equipped to participate in individual calls initiated by others. D.21.6.5.5 Selected subscriber radios shall be equipped to initiate Individual Calls. D.21.6.5.6 Selected subscriber radios shall be equipped to make unlimited individual calls to any other subscriber radio. D.21.6.5.7 An individual call shall be automatically cancelled after a pre-determined period of no PTT activity. D.21.6.5.8 Individual calls shall be trunked in a similar manner as a talkgroup call, and shall not have exclusive use of a talkpath for the duration of the entire conversation. Multi-Group Call Multi-Group calls shall allow multiple talkgroups to be affiliated to a single group. D.21.6.6.1 May 17, 2012 The subscriber radio shall have a means for the user to manually cancel the alarm. When a call is placed on the multi-group talkgroup, all talkgroups associated with the multi-group shall be assigned to a single voice channel for the conversation. Document 2 - Specification & Response Document Page 165 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.6.6.2 Every user involved in the multi-group call shall have talk-back capabilities for the duration of the conversation. D.21.6.6.3 The Multi-Group Call facility shall be programmable to allow for the following two (2) modes of operation: D.21.6.6.3.1 D.21.6.6.3.2 D.21.6.7 D.21.6.6.4 Initiating a multi-group call shall transmission trunk all calls in progress on affiliated talkgroups in order to facilitate the multi-group call. D.21.6.6.5 The Multi-Group call shall be automatically cancelled after a pre-determined time period. D.21.6.6.6 Dispatch consoles and subscriber radios shall have a means for the initiating user to manually cancel the Multi-Group call. System-Wide Call Dispatchers and selected subscriber units shall be equipped to initiate a call that will transmit simultaneously on all talkgroups on all sites or sub-systems. D.21.6.7.1 D.21.6.8 System-wide calls shall have the same two modes of operation (Ignore Mode and Wait Mode) as MultiGroup calls. System Access Priority Levels The Radio System shall be equipped for the assignment of at least eight levels of priority to talkgroups and individual Subscriber Radios. D.21.6.8.1 May 17, 2012 Ignore Mode. If a user initiates a multigroup call, calls in progress on affiliated talkgroups will be ignored. The multigroup call will not wait for units in those talkgroups to de-key and therefore those transmitting units will not hear the multi-group call until they de-key. Wait Mode. If a user initiates a multigroup call, calls that are in progress will cause the multi-group call to be placed in queue until all participating talkgroups have finished their transmissions. Talkgroups and Subscriber Radios having higher levels of priority shall receive preferential access to the Radio System compared to those having lower levels of priority. Document 2 - Specification & Response Document Page 166 of 399 Maricopa County, Arizona D.21.6.9 D.21.6.10 12030-RFP P25 Radio System Infrastructure Upgrade D.21.6.8.2 Subscriber radios and talkgroups that are in emergency status shall have the highest level of priority. D.21.6.8.3 Priority levels for each talkgroup and individual radio unit may be determined or modified through a System Administrator’s terminal by authorized system administrators and authorized service personnel. Dynamic Talkgroup Reassignment Dynamic reassignment of mobile and portable radios shall be provided. This function shall allow units from different talkgroups to be regrouped into a common talkgroup. D.21.6.9.1 Preprogramming of regrouping functions to allow rapid regrouping of large numbers of users shall be provided. D.21.6.9.2 Regrouping shall be accomplished through a system manager’s terminal by properly authorized personnel Channel Partitioning The Radio System shall be equipped to direct or steer talkgroup and individual calls to a single channel or group of channels within a multicast site or simulcast cell. D.21.6.10.1 D.21.6.11 Site Access by Talkgroup The Radio System shall be equipped to permit or deny access to a particular multicast site or simulcast cell based on the individual subscriber radio PTT ID or the individual subscriber radio's current talkgroup affiliation. D.21.6.11.1 D.21.6.12 May 17, 2012 These parameters shall be configurable by the System Administrator on a talkgroup-by-talkgroup basis. These parameters shall be configurable by the System Administrator on a talkgroup-by-talkgroup basis and by individual PTT IDs. Optional Over-the-Air Programming ("OTAP") At the discretion of the County, the County may require that the Radio System be equipped to remotely re-program subscriber radio equipment personalities and feature sets. D.21.6.12.1 OTAP may be performed on an individual subscriber-bysubscriber basis, or subscribers may be re-programmed in batches. D.21.6.12.2 OTAP shall not interfere with voice communications or reduce the voice traffic capacity of the Radio System. Document 2 - Specification & Response Document Page 167 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.6.12.3 If voice traffic causes the OTAP subsystem to halt reprogramming of a subscriber radio, re-programming shall resume where it left off upon cessation of the voice traffic. D.21.6.12.4 A means shall be provided for the OTAP subsystem to verify that a radio has been correctly programmed prior to issuance of the command to activate the new programming. D.21.6.12.5 The user of the subscriber radio being re-programmed shall, prior to issuance of the command to activate the new programming, have the option to accept or not accept the new programming. D.21.7 Master Network Switch D.21.7.1 The entire Trunked/LMR Subsystem shall be managed by a Master Network Switch (MNS) that allocates and manages the communications talkpaths and performs other essential functions. D.21.7.1.1 D.21.7.2 D.21.7.3 May 17, 2012 The Primary Master Network Switch shall be located at the Durango Site. A fully redundant MNS in a location geographically separated from the Primary MNS shall be provided. D.21.7.2.1 The Redundant MNS shall automatically and immediately take over control of the Radio System in the event of a failure of the Primary MNS. D.21.7.2.2 The Redundant MNS shall be located at the County's off-site backup data center. Details of the backup data center are provided in Document 3 - Confidential Supplement. Equipment cabinets used at the backup data center shall be Chatsworth Products, Inc. model number TS10005701 (note: this model number references a custom cabinet configuration). Cabinets shall contain American Power Conversion model AP8841 Metered Rack Power Distribution Units. Multiple Levels of Redundancy The Primary MNS and the Redundant MNS each shall have multiple levels of redundancy that require the failure of multiple components in one MNS before its operation is sufficiently degraded to require switchover to the other. Document 2 - Specification & Response Document Page 168 of 399 Maricopa County, Arizona D.21.7.4 12030-RFP P25 Radio System Infrastructure Upgrade Manual switching between the Primary MNS and the Redundant MNS shall also be provided. D.21.7.4.1 Manual switchover between the Primary MNS and the Redundant MNS shall be a manually-initiated automatic procedure that does not require manual start-up or shutdown of individual components to accomplish. D.21.7.4.2 There shall be safeguards in place to prevent unauthorized persons from initiating a manual switchover. D.21.7.5 Completion of switchover (manually or automatically) and return to normal operating conditions shall be accomplished in no more than 10 seconds. D.21.7.6 Subscriber radio equipment shall maintain their current site affiliations during switchover. Subscriber radio equipment shall not be forced to re-affiliate after a switchover has occurred. D.21.7.7 System administrators and maintenance personnel shall monitor alarms, access diagnostic, configuration and programming functions, perform database maintenance and all other monitoring and maintenance functions of the MNS and the Trunked LMR Subsystem through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.21.8 Network Components Servers, switches, routers and other network components shall be Commercial Off the Shelf ("COTS") equipment to the greatest extent possible. D.21.8.1 The capability for maintenance personnel to monitor alarms and access diagnostic and programming functions shall be provided through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.21.9 Base Stations/Repeater Stations Base stations/repeater stations shall be the manufacturer's highest tier models, suitable for operation under harsh environmental conditions of temperature and humidity and in high RF environments. D.21.9.1 Transmitters shall comply with all applicable FCC Rules and Regulations. D.21.9.2 Transmitters shall be equipped with two-stage (minimum) isolators to prevent the generation of intermodulation products. D.21.9.2.1 May 17, 2012 Isolators may be internal or external. Document 2 - Specification & Response Document Page 169 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.9.3 Transmitters shall be the lowest-power configuration available that satisfies the coverage requirements. D.21.9.4 Trunked transmitters and receivers shall be equipped for both P25 Phase 2 (TDMA) with backward compatibility to P25 Phase 1 (FDMA) operation. D.21.9.5 Simulcast transmitters shall automatically compensate for changes in simulcast timing caused by changes in IP routing. D.21.9.6 Simulcast timing parameters shall be adjustable by authorized maintenance personnel through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.21.9.7 Base Station/Repeater alarms, programming and diagnostics shall be accessible and adjustable by authorized maintenance personnel through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.21.10 Receiver Comparators D.21.10.1 Receiver comparators shall examine the incoming data stream from each receiver on a packet-by-packet basis, selecting the highest-quality packets from all receivers and then re-assembling them into a single output data stream. D.21.10.2 Receiver comparators shall provide an indication of a failed receiver, failed connectivity and receiver activity. These indications shall be available to maintenance personnel through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.21.10.3 Receiver comparators shall automatically compensate for changes in IP routing. D.21.10.4 The capability for system administrators and maintenance personnel to monitor alarms, access diagnostic functions and independently disable, select or monitor each receiver shall be provided through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.21.11 Radio System Expansion Capabilities D.21.11.1 Network Expansion Capabilities In anticipation of future growth, the MNS and its associated network components shall be equipped for expansion to a minimum of 30% additional trunked simulcast cells and/or multicast sites without the purchase or installation of additional hardware or additional software. D.21.11.2 May 17, 2012 Simulcast Cell Expansion Capabilities In anticipation of future growth, each simulcast cell and associated network components shall be equipped for expansion to a minimum of Document 2 - Specification & Response Document Page 170 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade 30% additional repeater sites without the purchase or installation of additional hardware or additional software (other than that required to equip the new site(s)). D.21.11.3 Radio Channel/Site Expansion Capabilities In anticipation of future growth, each repeater site and associated network components shall provide for expansion to a minimum of 30% additional base stations/repeaters without the purchase or installation of additional hardware or additional software (other than the additional base stations/repeaters). D.21.12 Base Station/Repeater Antennas D.21.12.1 Antennas, particularly at high sites, shall have appropriate amounts of downtilt and/or null-fill to prevent weak signal strength and poor coverage in areas closest to the Antenna Sites. D.21.12.2 Antennas shall be designed for survival at a minimum wind speed of 100 MPH. D.21.12.3 Antenna radiating elements shall be enclosed in a heavy-duty, weathertight, fiberglass radome. D.21.12.4 Antenna elements shall be DC grounded for lightning protection. D.21.12.5 RF connectors shall be type "N" or type "DIN" only. D.21.12.6 Antenna input power rating shall be a minimum of 125% of the total instant combined power with all transmitters operating simultaneously. D.21.13 Coaxial Cable Specifications D.21.13.1 Coaxial cable for Trunked/LMR transmit and receive antenna system(s) shall have a solid corrugated copper outer conductor, solid copper or copper-plated aluminum inner conductor, weatherproof and ultravioletresistant outer jacket and low-density foam dielectric, CommScope “AVA” series or approved equal. D.21.13.1.1 May 17, 2012 The use of coaxial cable with braided outer conductor is prohibited. D.21.13.2 The maximum acceptable attenuation for any length run of coaxial cable in a receiver antenna system shall be 1.9 dB, measured at 866 MHz, not including losses for connectors, coaxial jumpers or other antenna system elements. D.21.13.3 Coaxial cables that are to be installed within occupied buildings shall have a fire-retardant, low-smoke, low-halogen outer jacket, rated CATVR or CATVP per the National Electrical Code (NFPA 70). Document 2 - Specification & Response Document Page 171 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.13.4 Coaxial cables to be run in air plenums and tunnels shall have a fireretardant, low-smoke, low-halogen outer jacket, rated CATVP per the National Electrical Code (NFPA 70). D.21.13.5 Connectors for all coaxial cables shall be the appropriate type and gender (example: Type N female) for the required connection to be made and shall be the manufacturer's recommended connector for the cable being used. D.21.13.6 D.21.13.7 D.21.13.5.1 Connector types shall be Type N or DIN only. D.21.13.5.2 Use of barrel connectors, adapters and gender-changers shall not be permitted. UHF and Mini-UHF connectors are not acceptable for base station transmit and receive antenna systems. D.21.13.5.3 Connectors shall be designed and installed for minimum generation of intermodulation products. Coaxial Jumpers D.21.13.6.1 Coaxial cable jumpers used for interconnections between equipment within the equipment space shall be CommScope SureFlexTM factory-assembled cable assemblies (or approved equal) having fully soldered connectors and utilizing CommScope FSJ series superflexible coaxial cable (or approved equal). D.21.13.6.2 Coaxial cable jumpers used within equipment spaces shall have a fire-retardant outer jacket, rated CATVR or CATVP per the National Electrical Code (NFPA 70). D.21.13.6.3 Coaxial cable jumpers used within occupied buildings shall have a fire-retardant, low-smoke, low-halogen outer jacket, rated CATVR or CATVP per the National Electrical Code (NFPA 70). D.21.13.6.4 The use of coaxial cable jumpers with braided outer conductor is prohibited. Coaxial Cables Used for Other Than Antenna Systems The types of coaxial cables and connectors used for short runs for uses other than antenna systems shall be at the discretion of the Contractor, except that all coaxial cables shall have a fire-retardant outer jacket. D.21.14 Transmitter Combiner Specifications Outputs from the transmitters of all 700 MHz and 800 MHz base stations at each site shall be combined into a single output and routed to a single antenna, unless frequency May 17, 2012 Document 2 - Specification & Response Document Page 172 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade spacing makes this impractical. Transmitter combiners shall comply with the following specifications: D.21.14.1 Combiners shall incorporate dual-stage ferrite isolators on each input. D.21.14.2 Each isolator load resistor shall be rated to dissipate the entire rated transmitter output power. D.21.14.3 TX to TX isolation shall be 75 dB minimum, or greater if required to prevent harmful interference. D.21.14.4 Antenna to TX isolation shall be 70 dB minimum, or greater if required to prevent harmful interference. D.21.14.5 Maximum rated RF input power (per transmitter) shall be no less than 150 percent of the base station transmitter maximum power output rating. D.21.14.6 Harmonics and intermodulation products shall be suppressed by a minimum of 70 dB, or greater if required to prevent harmful interference. D.21.15 Receiver Multicoupler Specifications The receivers of all 700 MHz and 800 MHz base stations at each site shall be fed from a single antenna through a receiver multicoupler. The receiver multicoupler shall comply with the following specifications: D.21.15.1 The receiver multicoupler shall include a bandpass pre-selector to attenuate signals outside the desired frequency band. D.21.15.2 Isolation between output ports shall be 20 dB minimum. D.21.15.3 A low-noise preamplifier shall be incorporated. Noise figure shall be 3.0 dB or less. Amplifiers shall use GaAsFET, HEMT or other low-noise devices, not bipolar devices. D.21.15.4 3rd Order Intercept Point shall be +40 dBm or greater. D.21.15.5 The receiver multicoupler shall have an isolated test port. D.21.15.6 The receiver multicoupler shall be mountable in a standard 19 inch EIA equipment rack. D.21.16 Tower-Top Amplifier Specifications Tower-Top Amplifiers ("TTAs") shall: May 17, 2012 D.21.16.1 Have adjustable gain. D.21.16.2 Have a low noise figure of 3.0 dB or less. Document 2 - Specification & Response Document Page 173 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.16.3 Have lightning and transient suppression devices installed on its RF input, RF output and power input ports within or immediately adjacent to the TTA. D.21.16.4 Withstand extremes of weather, including temperatures of 0 deg. to +140 deg. F., rain, wind, dust and snow while remaining fully functional and meeting all manufacturer's specifications. D.21.16.5 TTA housings shall be independently connected to the Site exterior ground system. Use of the coaxial cable outer conductor as the primary ground conductor for the TTA is not acceptable. D.21.17 Optional Upgrade of Bi-Directional Amplifier Systems The buildings currently equipped with BDAs are listed in Section B.9. The County may elect to have the Contractor upgrade the existing BDAs to be compatible with the new Radio System, including any upgrades necessary to existing "leaky coax" or distributed antenna systems in order to maintain the same indoor coverage as the current BDA systems. Respondents will be given an opportunity to inspect the existing BDA systems. D.21.17.1 Cables (coaxial or otherwise) that are to be installed within occupied buildings shall have a fire-retardant, low-smoke, low-halogen outer jacket, rated CATVR or CATVP per the National Electrical Code (NFPA 70). D.21.17.2 Cables (coaxial or otherwise) to be run in air plenums and tunnels shall have a fire-retardant, low-smoke, low-halogen outer jacket, rated CATVP per the National Electrical Code (NFPA 70). D.21.17.3 All cabling shall comply with the requirements of Section D.2.3 of this document. D.21.17.4 All cabling shall comply with the National Electrical Code, the Arizona Building Code, and all applicable local laws, regulations, codes and standards. D.21.17.5 BDA system design shall account for amplifier propagation delays that may cause harmful interference in areas where signals from the BDA overlap with signals from the outside. D.21.18 Encryption The Radio System shall be equipped to encrypt communications in compliance with applicable P25 standards. D.21.18.1 Encryption type shall be 256-bit AES, compliant with National Institute of Standards and Technology publication FIPS-197 (latest revision). D.21.18.1.1 May 17, 2012 Cryptographic modules shall comply with the requirements for Security Level 1 specified in National Document 2 - Specification & Response Document Page 174 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Institute of Standards and Technology publication FIPS140-2. D.21.18.2 Digitally encrypted voice communications shall have a radio coverage range that is equal to the performance in the non-encrypted ("clear") mode. D.21.18.3 Audio quality in the encrypted mode shall be equal to audio quality in the clear mode. D.21.18.4 The Contractor shall provide Key Variable Loaders ("KVLs") that comply with applicable P25 standards. D.21.18.5 The Contractor shall provide an encryption key management facility ("KMF") that allows for the generation and distribution of cryptographic key material to subscriber equipment radios and infrastructure devices of the new radio system. The KMF shall include the following features: D.21.18.6 D.21.18.5.1 Shall remotely change (re-key) radios using Over-theAir-Rekeying ("OTAR") over the new radio network. D.21.18.5.2 Shall be equipped to generate and distribute an Advanced Encryption Standard (AES) 256 bit algorithm key via OTAR and KVL. D.21.18.5.3 The key management system shall be equipped to exchange encryption key material with different manufacturer’s KMFs utilizing a KVL. D.21.18.5.4 The KMF shall generate automatic audit reports that include the radio serial number, encryption key identification and last rekey date for each subscriber or other device that has been issued an encryption key(s). D.21.18.5.5 Interoperability with other manufacturer's subscriber radio equipment: The KMF shall have the ability to perform OTAR functions for any P25 compliant equipment that has OTAR and AES capabilities. End-to-End Encryption An encrypted message shall remain encrypted from the point of origin (a dispatch console workstation or a subscriber radio) to its final destination (a subscriber radio or a dispatch console workstation). The message shall not be decrypted and re-encrypted at an intermediate point. D.21.19 System Access and Security The Radio System shall be designed and implemented to be accessed only by authorized users and devices. May 17, 2012 Document 2 - Specification & Response Document Page 175 of 399 Maricopa County, Arizona D.21.19.1 12030-RFP P25 Radio System Infrastructure Upgrade Prevention of Unauthorized Access The Radio System shall incorporate multiple features that prevent access to the Radio System by unauthorized users. D.21.19.1.1 Access points to the Radio System through user computer workstations shall be locked down by both the computer MAC address and by user password authentication. D.21.19.1.2 Points where the Radio System network may be connected to other computer networks shall be protected by firewalls and intrusion detection devices. D.21.19.1.3 A database of currently authorized subscriber radio PTT IDs shall be maintained and access shall automatically be denied to subscriber radios whose PTT ID is not authorized. D.21.19.1.4 Radio System components shall not be physically placed in locations where access by persons not authorized to use, maintain or administer the Radio System is unrestricted. D.21.19.1.4.1 D.21.19.2 Protection Against Malware The Radio System shall be protected against infection by viruses, trojans, spyware and other malware through the use of anti-malware software. D.21.19.2.1 D.21.19.3 Call boxes are exempt from this requirement. See Section D.21.23. Anti-malware software versions and malware databases shall be kept current at all times. Disablement of Individual Radios The Radio System shall be equipped to manually disable selected individual subscriber radios by authorized system administrators or authorized maintenance personnel. D.21.20 GPS Location Reporting Capability Certain subscriber radios shall be equipped with the capability to report their current GPS location. See Section E, Subscriber Radio Equipment Technical & Functional Specifications. D.21.20.1 May 17, 2012 The Radio System shall capture the transmitted location information and format it for input into the mapping system which is a part of the County's new Computer-Aided-Dispatching ("CAD") system. Document 2 - Specification & Response Document Page 176 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.20.1.1 Details of the County's new CAD system can be found in Document 3, Confidential Supplement. D.21.20.2 The Radio System shall output the properly-formatted location information at a point of demarcation that is acceptable to the County. D.21.20.3 A means shall be provided for dispatchers to remotely cause a single selected subscriber radio to report its current location. D.21.20.4 D.21.20.5 D.21.20.3.1 This feature shall be easily accessible by each dispatcher through their dispatch console workstation GUI. D.21.20.3.2 Activation of the feature shall cause the selected subscriber radio to report its location one time only. A means shall be provided for dispatchers to cause a single selected subscriber radio to begin reporting its current location with every PTT. D.21.20.4.1 A complementary feature shall also be provided to cause the selected subscriber radio to cease reporting its current location with every PTT and to return to normal operation. D.21.20.4.2 These features shall be easily accessible by each dispatcher through their dispatch console workstation GUI. Upon activation of a subscriber radio's emergency button, that subscriber radio will automatically be commanded to begin reporting its current location with every PTT. D.21.20.5.1 Upon clearing of the emergency, the subscriber radio will automatically be commanded to cease reporting its current location with every PTT and to return to normal operation. D.21.20.6 Multiple subscriber radios shall be permitted to be in the "report location with every PTT" mode at any given time. D.21.20.7 If a subscriber radio has been in the "report location with every PTT" mode for longer than a pre-determined time period, that Subscriber Radio shall be automatically commanded to cease reporting its current location with every PTT and to return to normal operation. D.21.20.7.1 The time period that a subscriber radio may remain in the "report location with every PTT" mode shall be configurable by an authorized System Administrator from one hour to 24 hours. D.21.21 Emergency Consoles at Jails May 17, 2012 Document 2 - Specification & Response Document Page 177 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade The nine Maricopa County jails are equipped with emergency consoles as described in Section B.7. The Contractor shall replace these emergency consoles with new consoles having the same features and functions, but are compatible with the new Radio System. D.21.22 Interoperability Features D.21.22.1 The County has reached an agreement with RWC, TRWC and YRCS to assign four trunked talkgroups per system for interoperability purposes. These four talkgroups will be bridged between the systems using an analog audio bridge being supplied and installed by others. D.21.22.1.1 D.21.22.2 D.21.22.3 D.21.22.4 May 17, 2012 The Contractor shall provide four analog conventional interfaces at Thompson Peak, bridged to trunked talkgroups in the new Radio System. The Contractor shall provide and install the following at Mt. Ord: D.21.22.2.1 A VHF analog conventional base station tuned to the Gila County Sheriff's frequency. D.21.22.2.2 An antenna system for the VHF base station, including an isolator and cavity filters for interference protection, and a lightning suppression device. D.21.22.2.3 An analog conventional interface connected to the VHF base station and bridged to a trunked talkgroup. The Contractor shall provide and install the following at Yarnell Hill: D.21.22.3.1 A VHF analog conventional base station tuned to the Yavapai County Sheriff's frequency. D.21.22.3.2 An antenna system for the VHF base station, including an isolator and cavity filters for interference protection, and a lightning suppression device. D.21.22.3.3 An analog conventional interface connected to the VHF base station and bridged to a trunked talkgroup. The Contractor shall provide and install the following at the site providing the best coverage on I-17 at the Yavapai County/Maricopa County border: D.21.22.4.1 A VHF analog conventional base station tuned to the Yavapai County Sheriff's frequency. D.21.22.4.2 An antenna system for the VHF base station, including an isolator and cavity filters for interference protection, and a lightning suppression device. Document 2 - Specification & Response Document Page 178 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.21.22.4.3 D.21.22.5 D.21.22.6 D.21.22.7 May 17, 2012 An analog conventional interface connected to the VHF base station and bridged to a trunked talkgroup. The Contractor shall provide and install the following at the site providing the best coverage of I-10 at the Pinal County/Maricopa County border: D.21.22.5.1 A VHF analog conventional base station tuned to the Pinal County Sheriff's frequency. D.21.22.5.2 An antenna system for the VHF base station, including an isolator and cavity filters for interference protection, and a lightning suppression device. D.21.22.5.3 An analog conventional interface connected to the VHF base station and bridged to a trunked talkgroup. The Contractor shall provide and install the following at the MCSO Dispatch Center: D.21.22.6.1 Five UHF control stations tuned to the Arizona DPS Metro East, Metro West, Metro Central, East Tac and West Tac channels. D.21.22.6.2 Antenna systems for the UHF control stations, including isolators and cavity filters for interference protection, and lightning suppression devices. D.21.22.6.3 Each control station shall be remotely controlled by the dispatch consoles. The Contractor shall provide conventional channel interface devices if necessary. D.21.22.6.4 MCSO dispatchers shall have the capability to patch the DPS control stations to trunked talkgroups when required. An automatic bridge shall not be provided. Bridges between trunked talkgroups and analog conventional interfaces shall be automatically set up and knocked down by the Radio System. D.21.22.7.1 The bridges shall remain in a knocked-down state if there are no subscriber radios actively affiliated with the associated trunked talkgroup. D.21.22.7.2 A bridge will be automatically set up and activated when one or more subscriber radios affiliate with the associated talkgroup. D.21.22.7.3 The analog conventional channel interfaces shall be resources that may be monitored and used by the dispatch consoles, but the monitoring of an analog Document 2 - Specification & Response Document Page 179 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade conventional interface by a dispatch console shall not cause the bridge to be set up and activated. D.21.22.8 The MNS and redundant MNS shall be capable of a future system-tosystem link to other P25 systems operated by other entities via the Project 25 Inter Subsystem Interface ("ISSI"). D.21.23 Call Boxes The Contractor shall replace all fourteen existing trunked call boxes which are used by the general public in certain designated recreational areas to contact the Sheriff's dispatcher to report a crime or other emergency. D.21.23.1 The existing call boxes shall be replaced with replacement units that will work with the new P25 Radio System infrastructure. D.21.23.2 The new call boxes shall maintain the same features and functions as the previous call boxes. D.21.23.2.1 When the "call" button is pressed, the call box sends an alert to the dispatcher that identifies the call box. D.21.23.2.2 The dispatcher then enters the ID of the call box into the control unit which sends a message to the call box activating it and enabling the PTT button. D.21.23.2.3 The dispatcher and the reporting party may then have a two-way PTT conversation. D.21.23.2.4 When the call is finished, the dispatcher deactivates the call box and it returns to a "ready" state. D.21.23.3 Call box alerts, identification of the calling call box, and dispatcher control of the call boxes shall be a feature of the dispatch console workstation GUI. D.21.23.4 Call boxes shall be solar powered with a battery backup. D.21.23.5 Call boxes shall withstand extremes of weather, including temperatures of 0 deg. to +125 deg. F., rain, wind, dust and snow while remaining fully functional and undamaged. D.21.23.6 In addition to the Call Boxes as specified, the Contractor may propose an alternative solution that provides essentially the same functionality and is less expensive or provides superior features than the solution specified. D.21.24 Control Stations for Communication with Sites in "Site Trunking" Mode The Contractor shall provide control stations programmed for both Sheriff's Department dispatch talkgroups (East and West) in order to maintain communications with sites that May 17, 2012 Document 2 - Specification & Response Document Page 180 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade have lost connectivity to the network or for any other reason are in "site trunking" mode. D.21.24.1 At least two control stations shall be provided at each of the following Sites: D.21.24.1.1 Thompson Peak D.21.24.1.2 White Tanks East D.21.24.1.3 Oatman Mountain D.21.24.1.4 Additional sites if necessitated by the Contractor's design. D.21.24.2 Each control station shall be remotely controlled from the Sheriff's Department dispatch consoles. D.21.24.3 Each control station shall also be remotely controlled by desktop remote control units located at each dispatch console at the Sheriff's dispatch center. D.21.24.3.1 May 17, 2012 The desktop remote control units shall be wired in parallel with each other and with the dispatch console interface(s) so that any one of them may activate the control stations at any time without having to manually switch between them. D.21.24.4 Control stations shall comply with the requirements of Section E.6. D.21.24.5 Antenna systems shall be provided for each control station, including isolators and cavity filters for interference protection, and lightning suppression devices. Document 2 - Specification & Response Document Page 181 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.21 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21 D.21.1 D.21.2 D.21.2.1 D.21.2.2 D.21.2.3 D.21.3 D.21.4 D.21.4.1 D.21.4.2 D.21.4.3 D.21.4.4 D.21.4.4.1 D.21.4.4.2 D.21.5 D.21.5.1 D.21.5.2 D.21.5.3 D.21.5.4 D.21.6 D.21.6.1 D.21.6.1.1 D.21.6.1.2 D.21.6.1.3 D.21.6.2 D.21.6.2.1 D.21.6.3 D.21.6.3.1 D.21.6.3.2 D.21.6.3.3 D.21.6.3.3.1 D.21.6.3.3.2 May 17, 2012 Document 2 - Specification & Response Document Page 182 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21.6.3.4 D.21.6.4 D.21.6.4.1 D.21.6.4.2 D.21.6.4.3 D.21.6.5 D.21.6.5.1 D.21.6.5.2 D.21.6.5.3 D.21.6.5.4 D.21.6.5.5 D.21.6.5.6 D.21.6.5.7 D.21.6.5.8 D.21.6.6 D.21.6.6.1 D.21.6.6.2 D.21.6.6.3 D.21.6.6.3.1 D.21.6.6.3.2 D.21.6.6.4 D.21.6.6.5 D.21.6.6.6 D.21.6.7 D.21.6.7.1 D.21.6.8 D.21.6.8.1 D.21.6.8.2 D.21.6.8.3 D.21.6.9 D.21.6.9.1 D.21.6.9.2 D.21.6.10 May 17, 2012 Document 2 - Specification & Response Document Page 183 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21.6.10.1 D.21.6.11 D.21.6.11.1 D.21.6.12 D.21.6.12.1 D.21.6.12.2 D.21.6.12.3 D.21.6.12.4 D.21.6.12.5 D.21.7 D.21.7.1 D.21.7.1.1 D.21.7.2 D.21.7.2.1 D.21.7.2.2 D.21.7.3 D.21.7.4 D.21.7.4.1 D.21.7.4.2 D.21.7.5 D.21.7.6 D.21.7.7 D.21.8 D.21.8.1 D.21.9 D.21.9.1 D.21.9.2 D.21.9.2.1 D.21.9.3 D.21.9.4 D.21.9.5 D.21.9.6 D.21.9.7 May 17, 2012 Document 2 - Specification & Response Document Page 184 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21.10 D.21.10.1 D.21.10.2 D.21.10.3 D.21.10.4 D.21.11 D.21.11.1 D.21.11.2 D.21.11.3 D.21.12 D.21.12.1 D.21.12.2 D.21.12.3 D.21.12.4 D.21.12.5 D.21.12.6 D.21.13 D.21.13.1 D.21.13.1.1 D.21.13.2 D.21.13.3 D.21.13.4 D.21.13.5 D.21.13.5.1 D.21.13.5.2 D.21.13.5.3 D.21.13.6 D.21.13.6.1 D.21.13.6.2 D.21.13.6.3 D.21.13.6.4 D.21.13.7 D.21.14 May 17, 2012 Document 2 - Specification & Response Document Page 185 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21.14.1 D.21.14.2 D.21.14.3 D.21.14.4 D.21.14.5 D.21.14.6 D.21.15 D.21.15.1 D.21.15.2 D.21.15.3 D.21.15.4 D.21.15.5 D.21.15.6 D.21.16 D.21.16.1 D.21.16.2 D.21.16.3 D.21.16.4 D.21.16.5 D.21.17 D.21.17.1 D.21.17.2 D.21.17.3 D.21.17.4 D.21.17.5 D.21.18 D.21.18.1 D.21.18.1.1 D.21.18.2 D.21.18.3 D.21.18.4 D.21.18.5 D.21.18.5.1 May 17, 2012 Document 2 - Specification & Response Document Page 186 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Standard Requirement Comply/ Section Exception D.21.18.5.2 D.21.18.5.3 D.21.18.5.4 D.21.18.5.5 D.21.18.6 D.21.19 D.21.19.1 D.21.19.1.1 D.21.19.1.2 D.21.19.1.3 D.21.19.1.4 D.21.19.1.4.1 D.21.19.2 D.21.19.2.1 D.21.19.3 D.21.20 D.21.20.1 D.21.20.1.1 D.21.20.2 D.21.20.3 D.21.20.3.1 D.21.20.3.2 D.21.20.4 D.21.20.4.1 D.21.20.4.2 D.21.20.5 D.21.20.5.1 D.21.20.6 D.21.20.7 D.21.20.7.1 D.21.21 D.21.22 D.21.22.1 May 17, 2012 Document 2 - Specification & Response Document Page 187 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21.22.1.1 D.21.22.2 D.21.22.2.1 D.21.22.2.2 D.21.22.2.3 D.21.22.3 D.21.22.3.1 D.21.22.3.2 D.21.22.3.3 D.21.22.4 D.21.22.4.1 D.21.22.4.2 D.21.22.4.3 D.21.22.5 D.21.22.5.1 D.21.22.5.2 D.21.22.5.3 D.21.22.6 D.21.22.6.1 D.21.22.6.2 D.21.22.6.3 D.21.22.6.4 D.21.22.7 D.21.22.7.1 D.21.22.7.2 D.21.22.7.3 D.21.22.8 D.21.23 D.21.23.1 D.21.23.2 D.21.23.2.1 D.21.23.2.2 D.21.23.2.3 May 17, 2012 Document 2 - Specification & Response Document Page 188 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.21 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.21.23.2.4 D.21.23.3 D.21.23.4 D.21.23.5 D.21.23.6 D.21.24 D.21.24.1 D.21.24.1.1 D.21.24.1.2 D.21.24.1.3 D.21.24.1.4 D.21.24.2 D.21.24.3 D.21.24.3.1 D.21.24.4 D.21.24.5 {End Section D.21} May 17, 2012 Document 2 - Specification & Response Document Page 189 of 399 Maricopa County, Arizona D.22 12030-RFP P25 Radio System Infrastructure Upgrade Dispatch Console Subsystem Functional & Technical Specifications D.22.1 Features and Functions D.22.1.1 The dispatch console subsystem shall be tightly integrated into the Radio System. D.22.1.2 The dispatch console subsystem shall utilize Ethernet and Internet Protocol for connectivity with the rest of the Radio System. D.22.1.3 The dispatch console subsystem shall continuously run diagnostics to assure proper performance and shall be equipped to automatically take corrective action to restore proper operation should a failure be detected. D.22.1.4 D.22.1.3.1 An alarm shall be generated when component failures occur. D.22.1.3.2 All alarms and diagnostic functions shall be available through the Diagnostic and Monitoring System specified in Section D.24 of this document. The dispatch console subsystem shall be configured for fully-redundant “hot-standby” operation. D.22.1.4.1 D.22.1.5 May 17, 2012 Failure of any major component will automatically trigger switchover to a redundant component, without loss of communications capability. Dispatch Console Workstation Hardware Dispatch console workstations shall have the following features: D.22.1.5.1 A LCD monitor, minimum 24 inch diagonal dimension. D.22.1.5.2 A heavy-duty keyboard and mouse. D.22.1.5.3 A microphone, either desk or gooseneck mounted, directional, high fidelity, frequency response 20 Hz to 10,000 Hz or more, maximum 1% distortion at normal sound pressure levels. D.22.1.5.4 Separate select and unselect speakers with individual volume controls. D.22.1.5.5 Two headset jacks with microphone input. Insertion of headset plug into jack automatically disables gooseneck microphone. D.22.1.5.6 Dual-pedal footswitch that may be customprogrammed by the user. Example: the left pedal transmits on the selected channel, while the right pedal transmits on a user-defined unselected channel. Document 2 - Specification & Response Document Page 190 of 399 Maricopa County, Arizona D.22.1.6 12030-RFP P25 Radio System Infrastructure Upgrade Dispatch Console Graphical User Interface ("GUI") Features of the GUI shall include: D.22.1.6.1 Dedicated windows representing all talkgroups, conventional channel interfaces and other functions and all information available at each console. D.22.1.6.2 Fully user-customizable appearances of on-screen talkgroup, channel function and informational windows. D.22.1.6.2.1 May 17, 2012 Once customized for the individual user, screen configurations may be saved and recalled when desired. D.22.1.6.3 Instant-transmit control for each talkgroup and conventional channel. D.22.1.6.4 Simultaneous selection of multiple radio channels ("multi-select"). Microphone audio is simultaneously routed to all selected channels, and all selected channel receive audio is routed to the Select speaker and headset(s). D.22.1.6.5 A call indicator (indicating a call from the field is being received) and a busy indicator (indicating another dispatcher is transmitting) shall be provided for each talkgroup and conventional channel. D.22.1.6.6 An Encrypted/Clear selector for each talkgroup. D.22.1.6.6.1 The talkgroup control window shall clearly and prominently indicate whether the talkgroup is currently in encrypted or clear mode. D.22.1.6.6.2 Talkgroups shall be programmable to be either encrypted or clear by default. Manual selection of encrypted or clear by the dispatcher shall override the default programming. D.22.1.6.6.3 If the default is manually changed by the dispatcher, the talkgroup shall automatically revert to the default mode of operation after a predetermined time period which shall be configurable by an authorized System Document 2 - Specification & Response Document Page 191 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Administrator from one hour to 24 hours. D.22.1.6.7 D.22.1.6.8 D.22.1.6.9 D.22.1.7 May 17, 2012 A PTT ID display and PTT ID history. The PTT ID of the last subscriber radio to transmit shall be prominently displayed on the GUI. By scrolling, the dispatcher shall see a history of the last 50 PTT IDs. D.22.1.6.7.1 A separate PTT ID display shall be provided for the selected channel, and for each talkgroup and conventional channel. D.22.1.6.7.2 PTT ID entries shall also display a time stamp. D.22.1.6.7.3 If the PTT ID has been assigned an alphanumeric alias, the alias shall be displayed rather than an electronic serial number or trunking ID code that would require the dispatcher to manually look up the user assigned to that radio. D.22.1.6.7.4 Aliases shall be maintained in a single, common database accessible to all workstations. D.22.1.6.7.5 Aliases shall have a maximum length of no less than sixteen characters. D.22.1.6.7.6 Aliases may contain any character defined in the ASCII character set. Multiple alert tones shall be available to be transmitted over any talkgroup or conventional channel. A minimum of three tones shall be provided: D.22.1.6.8.1 A steady 1000 Hz tone D.22.1.6.8.2 A warbling tone D.22.1.6.8.3 A pulsed alert tone. Control of additional functions including but not limited to call boxes and GPS location reporting as described elsewhere in this document. The Dispatch Console subsystem shall accept a time synchronization input in conformance with NENA Standard 04-002. Document 2 - Specification & Response Document Page 192 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.22.2 Emergency Alarm Functionality D.22.2.1 Upon receipt of an emergency signal from an end-user radio, an audible and visual alert shall be presented on all consoles that are monitoring that talkgroup, whether selected or unselected. D.22.2.2 If no console is monitoring the talkgroup, the emergency signal shall be routed to one of the following: D.22.2.2.1 All consoles D.22.2.2.2 No consoles (emergency signal is discarded) D.22.2.2.3 One or more consoles that have been pre-selected to receive emergency signals from that talkgroup in the event the talkgroup is un-monitored D.22.2.3 The disposition of emergency signals from un-monitored talkgroups shall be configurable by an authorized system administrator on a talkgroup-by-talkgroup basis. D.22.2.4 The routing of emergency signals may be changed at any time by an authorized system administrator without the need for a re-start of software or hardware. D.22.2.4.1 D.22.2.5 The response time to display the emergency condition at the console position(s) shall not exceed 3 seconds. D.22.2.6 The display shall identify the PTT ID alias (if one is defined) of the subscriber radio initiating the emergency signal. Otherwise, the PTT ID shall be displayed. D.22.2.7 The audible and visual alert shall continue to be displayed until the operator of one or more consoles acknowledge the emergency signal. D.22.2.8 Acknowledgement of the alarm at one console shall silence other consoles, but shall not cancel the emergency condition. D.22.2.9 A separate action shall be required to “clear” the emergency and return the system to normal operation. D.22.2.10 Acknowledgement of the alarm shall send an electronic message to the initiating subscriber radio which, if it is so programmed, shall cause it to activate a light or another display to indicate that a dispatcher has acknowledged the emergency signal. D.22.2.10.1 May 17, 2012 Changes shall take effect immediately. The electronic acknowledgement shall not take the place of, or interfere with, a voice acknowledgement that may be made by the dispatcher. Document 2 - Specification & Response Document Page 193 of 399 Maricopa County, Arizona D.22.2.11 12030-RFP P25 Radio System Infrastructure Upgrade The emergency condition shall be cleared by either of the following two methods (both methods shall be available and functional): D.22.2.11.1 An action by the dispatcher through the dispatch console workstation. D.22.2.11.2 An action by the user through the initiating user's subscriber radio. D.22.3 Console Patch Functionality D.22.3.1 Dispatch consoles shall have the capability to patch between: D.22.3.1.1 Any trunked talkgroup and one or more other trunked talkgroup D.22.3.1.2 One or more trunked talkgroups and one or more conventional channels D.22.3.1.3 Any conventional channel and one or more other conventional channel D.22.3.1.4 Any telephone line and any trunked talkgroup or conventional channel. D.22.3.2 There shall be no limit to the number of talkgroups or channels that may be included in a single patch. D.22.3.3 There shall be two types of console patches: D.22.3.3.1 Hard (permanently nailed-up by a system administrator without dispatcher action) D.22.3.3.2 Soft (temporarily made by a dispatcher). D.22.3.4 Active hard patches shall be displayed to the console operators through the console workstation GUI, but the console operator shall not have the capability to knock down the patch. D.22.3.5 A soft patch may be added to or removed from a hard patch at any time and in the same manner as any other soft patch. D.22.3.6 Talkgroups and conventional channels may be added to or removed from an existing hard or soft patch without interruption to patch communications. D.22.3.7 Often-used patch configurations may be stored and recalled for later use. D.22.3.7.1 May 17, 2012 Recall of a stored patch configuration shall be through the console workstation GUI via a drop-down box or other method convenient to the console operator. Document 2 - Specification & Response Document Page 194 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.22.4 Other Features and Functions D.22.4.1 Priority/Emergency Channel Marker A low volume tone pulsed regularly at user-defined intervals shall be available to indicate that the channel/talkgroup is handling emergency traffic. D.22.4.1.1 D.22.4.2 Individual Alert Capability Dispatcher console workstations shall have the ability to initiate Individual Alerts to any subscriber radio, regardless of current talkgroup affiliation. Please refer to Section D.21.6.4. D.22.4.2.1 D.22.4.3 The desired subscriber radio shall be selected by the PTT ID alias, if one is defined, or the PTT ID. Individual Call Capability Dispatcher console workstations shall have the ability to initiate an Individual Call to any subscriber radio, regardless of current talkgroup affiliation. Please refer to Section D.21.6.5. D.22.4.3.1 D.22.4.4 The tone shall be easily distinguishable from other tones used for other functions. The desired subscriber radio shall be selected by the PTT ID alias, if one is defined, or the PTT ID. Instant Recall Recorder Selected dispatch console workstations shall include a software-based Instant Recall Recorder ("IRR") equipped to play back the last thirty minutes of conversation from any selected or unselected talkgroup. D.22.4.4.1 The IRR shall be equipped to play a message back at reduced speed, without a change in voice pitch. D.22.4.4.1.1 D.22.4.4.2 May 17, 2012 The range in speed variation shall be at least 2:1, but a greater range is desirable. The control panel shall contain the following controls: D.22.4.4.2.1 Talkgroup or Channel Select D.22.4.4.2.2 Fast Rewind D.22.4.4.2.3 Fast Forward D.22.4.4.2.4 Pause D.22.4.4.2.5 Restore D.22.4.4.2.6 Save D.22.4.4.2.7 Clear Document 2 - Specification & Response Document Page 195 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.22.4.4.2.8 D.22.4.5 D.22.4.4.3 The IRR control window shall have an alphanumeric display indicating such information as message length, message ID, radio user PTT ID alias or PTT ID and time. D.22.4.4.4 The IRR control functions shall be easily accessible through the dispatch console workstation GUI. Cross-Mute When one dispatch console workstation transmits on a particular talkgroup or conventional channel, the audio output of other workstations in the vicinity monitoring the same talkgroup or channel shall be muted to prevent feedback. Workstations not in the vicinity shall not be muted. D.22.4.5.1 D.22.4.6 Volume Control The other workstations to be muted shall be defined in the configuration file for each workstation. Intercom Capability D.22.4.6.1 An intercom function between workstations shall be provided. Intercom audio shall not override radio or telephone audio. D.22.4.6.2 An intercom function between workstations and external locations (examples: front door or sally port) shall be provided. D.22.4.7 Telephone Interface The capability to answer and place calls on administrative telephones or ring-down lines shall be provided. Telephone audio shall be available through the dispatch console headset jacks. D.22.4.8 Auxiliary Controls Auxiliary controls for a minimum of eight doors and other external devices per dispatch center location shall be provided. D.22.4.9 Supervisory Capability The supervisor's dispatch console workstation(s) shall have the ability to override or disable the other console dispatch workstations in compliance with FCC Rules and Regulations. D.22.4.10 Loading of Encryption Keys The dispatch console subsystem shall accept the loading of encryption keys through the Radio System KMF and a KVL. D.22.5 Logging Recorder The Radio System shall be interfaced to the existing Nice Systems NL-2000 logging recorders at Sheriff's Dispatch and Adult Probation dispatch. May 17, 2012 Document 2 - Specification & Response Document Page 196 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.22.6 Existing Control Stations and Base Stations The County operates a number of control stations and base stations located at dispatch centers and various other locations that are used for various purposes. D.22.6.1 The Contractor shall replace existing trunked control stations that are not capable of P25 Phase 2 TDMA operation with new control stations. D.22.6.2 Control stations that are capable of but not equipped for P25 Phase 2 operation shall be equipped for P25 Phase 2 operation or replaced at the Contractor's discretion. D.22.6.3 Existing control stations and base stations that are controlled through the existing dispatch consoles shall be connected and controlled in the same manner to the new dispatch consoles. D.22.6.3.1 May 17, 2012 The Contractor shall provide conventional channel interface devices if necessary. D.22.6.4 Existing control stations and base stations (both trunked and conventional) that are greater than seven years old shall be replaced with new control stations and base stations having the same functionality. D.22.6.5 Please refer to Appendix 10 for a list of existing control stations and base stations and their locations. Document 2 - Specification & Response Document Page 197 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.22 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.22 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.22 D.22.1 D.22.1.1 D.22.1.2 D.22.1.3 D.22.1.3.1 D.22.1.3.2 D.22.1.4 D.22.1.4.1 D.22.1.5 D.22.1.5.1 D.22.1.5.2 D.22.1.5.3 D.22.1.5.4 D.22.1.5.5 D.22.1.5.6 D.22.1.6 D.22.1.6.1 D.22.1.6.2 D.22.1.6.2.1 D.22.1.6.3 D.22.1.6.4 D.22.1.6.5 D.22.1.6.6 D.22.1.6.6.1 D.22.1.6.6.2 D.22.1.6.6.3 D.22.1.6.7 D.22.1.6.7.1 D.22.1.6.7.2 D.22.1.6.7.3 D.22.1.6.7.4 May 17, 2012 Document 2 - Specification & Response Document Page 198 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.22 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.22.1.6.7.5 D.22.1.6.7.6 D.22.1.6.8 D.22.1.6.8.1 D.22.1.6.8.2 D.22.1.6.8.3 D.22.1.6.9 D.22.1.7 D.22.2 D.22.2.1 D.22.2.2 D.22.2.2.1 D.22.2.2.2 D.22.2.2.3 D.22.2.3 D.22.2.4 D.22.2.4.1 D.22.2.5 D.22.2.6 D.22.2.7 D.22.2.8 D.22.2.9 D.22.2.10 D.22.2.10.1 D.22.2.11 D.22.2.11.1 D.22.2.11.2 D.22.3 D.22.3.1 D.22.3.1.1 D.22.3.1.2 D.22.3.1.3 D.22.3.1.4 May 17, 2012 Document 2 - Specification & Response Document Page 199 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.22 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.22.3.2 D.22.3.3 D.22.3.3.1 D.22.3.3.2 D.22.3.4 D.22.3.5 D.22.3.6 D.22.3.7 D.22.3.7.1 D.22.4 D.22.4.1 D.22.4.1.1 D.22.4.2 D.22.4.2.1 D.22.4.3 D.22.4.3.1 D.22.4.4 D.22.4.4.1 D.22.4.4.1.1 D.22.4.4.2 D.22.4.4.2.1 D.22.4.4.2.2 D.22.4.4.2.3 D.22.4.4.2.4 D.22.4.4.2.5 D.22.4.4.2.6 D.22.4.4.2.7 D.22.4.4.2.8 D.22.4.4.3 D.22.4.4.4 D.22.4.5 D.22.4.5.1 D.22.4.6 May 17, 2012 Document 2 - Specification & Response Document Page 200 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.22 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.22.4.6.1 D.22.4.6.2 D.22.4.7 D.22.4.8 D.22.4.9 D.22.4.10 D.22.5 D.22.6 D.22.6.1 D.22.6.2 D.22.6.3 D.22.6.3.1 D.22.6.4 D.22.6.5 {End Section D.22} May 17, 2012 Document 2 - Specification & Response Document Page 201 of 399 Maricopa County, Arizona D.23 12030-RFP P25 Radio System Infrastructure Upgrade Backhaul Subsystem Functional & Technical Specifications The Contractor shall provide and install a complete backhaul network to support the new Radio System and additional services as directed by the County. The existing County microwave network shall be completely replaced by the new backhaul network. D.23.1 Capacity The capacity of the backhaul network shall be sufficient to support the requirements of the new Radio System, plus telephone and data circuits to other County facilities now being supported by the existing microwave network, plus 30% additional capacity to accommodate future growth. Please see Appendix 14 for a listing of existing telephone and data circuits that shall continue to be supported by the new backhaul network. D.23.1.1 Each microwave link of fiber-optic link proposed for use in the Radio System shall receive a minimum of 30% more capacity than is required to support the initial capacity requirements. D.23.2 Optional Additional Capacity At the County's discretion, the County may require that each antenna site proposed for use in the Radio System receive a minimum usable bandwidth of 50 Mbps. Please see Appendix 14 for a listing of existing telephone and data circuits that shall continue to be supported by the new backhaul network. D.23.2.1 The Contractor shall prepare an alternative backhaul network design that meets this requirement should the County elect to pursue this option. D.23.3 Existing County Fiber Optic Network The Contractor may incorporate portions of the County's existing fiber-optic network into its design. Details of the County's fiber optic network are contained in Document 3, Confidential Supplement. The County will make arrangements and provide the necessary hardware for the Vendor's connection to the County's fiber optic loop for access to the County’s Backup data Center as shown in the diagram provided as part of Document 3 - Confidential Supplement. Access to each loop will be provided at the Durango Site and the Central Courts Building site, through the Cisco routers indicated above. The demarcation points shall be Gigabit Ethernet ports with RJ-45 connectors. In their proposals, vendors shall specify the bandwidth the proposed radio system will require for each connection to the County's fiber optic loop, and any special requirements there may be. The County will make arrangements and provide the necessary hardware for the Vendor's connection to the County's fiber optic network for connectivity to MCSO Dispatch, Adult Probation Dispatch, Animal Control Dispatch, Flood Control Alert Operations Center and MCDOT Dispatch. The demarcation points shall be Gigabit Ethernet ports with RJ-45 connectors. In their proposals, vendors shall specify the bandwidth each proposed dispatch center connection will require and any special requirements there may be. D.23.4 Ethernet and Internet Protocol May 17, 2012 Document 2 - Specification & Response Document Page 202 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade The backhaul network shall support Ethernet and IP-based services. D.23.4.1 A Time Division Multiplex ("TDM")-based network is not acceptable. D.23.4.2 The new backhaul network shall support a small number of existing TDM circuits for the foreseeable future. Please see Appendix 14 for a listing of existing telephone and data circuits that shall continue to be supported by the new backhaul network. D.23.4.3 The new backhaul network shall have the capability of supporting IP telephone service, Wide-Area-Network ("WAN") data traffic and video services without modification of the network. Bandwidth requirements to support future telephone, data and video systems have not been determined, but are not expected to exceed the 30% additional bandwidth capacity for future growth specified in Section D.23.1 of the specification or the 50 Mbps optional additional capacity specified in Section D.23.2. D.23.5 Multi-Protocol Label Switching The backhaul network shall utilize Multi-Protocol Label Switching ("MPLS") to support: D.23.5.1 Hierarchical Quality of Service ("HQoS") to provide guaranteed bandwidth for Radio System traffic and other mission-critical services. D.23.5.2 Restoration of traffic within 50 ms in the event of failure of a network node or link. D.23.5.3 Efficient usage of available bandwidth. Lower-priority services may occupy additional bandwidth if higher-priority services are idle. D.23.5.4 The ability to combine Ethernet/IP, TDM and other services into a single network. D.23.6 Redundancy and Reliability D.23.6.1 The backhaul network shall be designed in a loop configuration to the greatest extent possible. D.23.6.1.1 May 17, 2012 Multiple interconnected loops are acceptable. D.23.6.2 Network nodes not served by a loop shall be configured as "HotStandby," whereby a redundant component will immediately and automatically take over for the primary component in the event of a failure of the primary component. D.23.6.3 Overall backhaul network availability shall be a minimum of 99.999%. D.23.6.4 Individual microwave RF paths shall be designed for an availability of 99.9999% for a Bit Error Rate ("BER") of 1 X 10-6. Document 2 - Specification & Response Document Page 203 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.23.6.4.1 Diversity techniques shall be utilized when necessary to meet the availability requirement. D.23.6.4.2 Switching between diversity components shall be "hitless," causing no errors in the output data stream. D.23.6.4.3 A physical path survey shall be performed for each microwave path by a qualified path surveyor. D.23.6.4.4 Microwave RF path designs shall contain a tree growth factor of twenty feet to be added to measured tree heights at critical points along the microwave path. D.23.7 Microwave Equipment D.23.7.1 Microwave equipment shall be designed and manufactured to have an operational service life of a minimum of fifteen years. D.23.7.2 Equipment Specifications D.23.7.2.1 Microwave equipment shall be designed to meet all manufacturers' published specifications when operating in ambient temperatures of 32 deg. F to +120 deg. F. D.23.7.2.2 Microwave equipment shall continue to operate without failure over an ambient temperature range of 0 deg. F to +131 deg. F. D.23.7.2.3 Relative humidity: 5% to 95% non-condensing. D.23.7.2.4 Microwave equipment shall meet all manufacturers' published specifications at the altitude at which it will be installed. D.23.7.2.5 All equipment shall be securely mountable in a 19 inch EIA rack. D.23.7.2.6 All microwave equipment shall operate from a 48 VDC (nominal) power source. D.23.7.2.7 Ethernet I/O shall be via a standard RJ-45 data connector or optical interface. D.23.8 Fiber-Optic Equipment If the Contractor's design includes any portion of the County's existing network, the County will assist the Contractor in developing the requirements for the interface. D.23.8.1 The County will provide a suitable point of demarcation where the Contractor shall connect its equipment to the County network. D.23.9 Diagnostics, Controls and Alarms D.23.9.1 At a minimum, the following alarms shall be reported: May 17, 2012 Document 2 - Specification & Response Document Page 204 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.23.9.1.1 Failure of a node or link D.23.9.1.2 Failover to a redundant component D.23.9.1.3 Loss of network timing or synchronization D.23.9.1.4 Bit Error Rate of an individual node or link exceeds a pre-determined threshold value D.23.9.2 Diagnostic functions shall be available that will enable remote troubleshooting of faults down to the FRU level. D.23.9.3 The ability to manually and remotely initiate a switch-over to a redundant component shall be provided. D.23.9.4 Network nodes shall be remotely configurable by authorized maintenance personnel. D.23.9.5 Maintenance personnel shall have access to all diagnostics, controls and alarms through the Diagnostic and Monitoring System specified in Section D.24 of this document. D.23.10 Other Requirements D.23.10.1 All equipment in a particular category (example: microwave equipment) shall be of the same manufacturer. D.23.10.1.1 D.23.10.2 The backhaul network shall have its timing synchronized to a reference source of sufficient accuracy to meet the availability specification, voice audio quality specifications and ensure error-free transmission of voice, video and data. D.23.10.3 Each backhaul network node site shall be equipped with a voice telephone set which shall be an extension off of the existing County Private Branch Exchange ("PBX") telephone network and connected through the backhaul network. D.23.10.3.1 May 17, 2012 Equipment shall be of the same series or model to the greatest extent possible. The Contractor shall provide and install the equipment necessary to interface the County PBX equipment to the IP network. The County will be responsible for providing the site telephone, the site telephone interface equipment and the telephone switch interface equipment. At each site, the Vendor shall provide a demarcation point consisting of a Gigabit Ethernet port utilizing an RJ-45 connector where the County shall access the backhaul network. At the Durango Site and the Central Courts Building sites, the Vendor shall Document 2 - Specification & Response Document Page 205 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade provide similar ports for connection to the telephone switches, one port for each site. The final details of the site telephone and telephone switch interface with the backhaul network will be determined during the detailed design process after contract award. D.23.10.4 May 17, 2012 D.23.10.3.2 The County shall approve any such interface equipment prior to installation. D.23.10.3.3 The County shall provide the PBX extension circuits to a demarcation point to be specified by the County. Each backhaul network node shall be equipped with a service channel/orderwire unit with a speaker and a handset. D.23.10.4.1 The orderwire unit shall be able to selectively call any other orderwire unit connected to the network. D.23.10.4.2 The orderwire unit shall be able to broadcast a call to all other orderwire units connected to the network. Document 2 - Specification & Response Document Page 206 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.23 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.23 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Standard Comply Comply Comply Comply Standard Standard Standard Standard Requirement Comply/ Section Exception D.23 D.23.1 D.23.1.1 D.23.2 D.23.2.1 D.23.3 D.23.4 D.23.4.1 D.23.4.2 D.23.4.3 D.23.5 D.23.5.1 D.23.5.2 D.23.5.3 D.23.5.4 D.23.6 D.23.6.1 D.23.6.1.1 D.23.6.2 D.23.6.3 D.23.6.4 D.23.6.4.1 D.23.6.4.2 D.23.6.4.3 D.23.6.4.4 D.23.7 D.23.7.1 D.23.7.2 D.23.7.2.1 D.23.7.2.2 D.23.7.2.3 D.23.7.2.4 May 17, 2012 Document 2 - Specification & Response Document Page 207 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.23 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.23.7.2.5 D.23.7.2.6 D.23.7.2.7 D.23.8 D.23.8.1 D.23.9 D.23.9.1 D.23.9.1.1 D.23.9.1.2 D.23.9.1.3 D.23.9.1.4 D.23.9.2 D.23.9.3 D.23.9.4 D.23.9.5 D.23.10 D.23.10.1 D.23.10.1.1 D.23.10.2 D.23.10.3 D.23.10.3.1 D.23.10.3.2 D.23.10.3.3 D.23.10.4 D.23.10.4.1 D.23.10.4.2 {End Section D.23} May 17, 2012 Document 2 - Specification & Response Document Page 208 of 399 Maricopa County, Arizona D.24 12030-RFP P25 Radio System Infrastructure Upgrade Alarm and Diagnostic Subsystem Functional & Technical Specifications The Contractor shall provide a system to monitor the health and status of all Radio System equipment and components to assist technical and engineering staff in troubleshooting faults, predicting future faults, and performing remote programming, configuration and other functions. D.24.1 Consolidated System It is the intent of the County to have a single Alarm and Diagnostic subsystem for the entire Radio System rather than multiple alarm and diagnostic subsystems for individual subsystems and components. The Alarm and Diagnostic Subsystem shall consolidate all of the following: D.24.1.1 Alarm and status outputs from all equipment and components D.24.1.2 Analog and digital metering from all equipment and components D.24.1.3 Inputs and outputs of diagnostic functions of all equipment and components D.24.1.4 Historical reporting from all equipment and components D.24.1.5 Inputs and outputs of remote programming and configuration functions of all equipment and components. D.24.1.6 Outputs and inputs from SCADA remote terminal units placed at various locations within the Radio System. D.24.1.7 Functions to initiate manual switchover from primary to redundant components or vice versa. D.24.1.8 Manual disabling or re-enabling talkpaths or channels. D.24.2 Architecture The Alarm and Diagnostic Subsystem shall consist of: D.24.2.1 A Primary Server and a Redundant Server which processes and stores current and historical information. D.24.2.1.1 D.24.2.2 May 17, 2012 The Redundant Server shall automatically take over operation of the Alarm and Diagnostic Subsystem in the event of failure of the Primary. Multiple Alarm and Diagnostic Workstations which provide a GUI for: D.24.2.2.1 Display of current alarms D.24.2.2.2 Acknowledgement and reset of alarms D.24.2.2.3 Invocation of diagnostic processes and reporting of results Document 2 - Specification & Response Document Page 209 of 399 Maricopa County, Arizona D.24.2.3 12030-RFP P25 Radio System Infrastructure Upgrade D.24.2.2.4 Invocation of remote programming and configuration functions. D.24.2.2.5 Review of historical alarm and diagnostic data. D.24.2.2.6 Initiate manual switchovers and report results. A WAN to connect the Primary Server, Redundant Server and the Alarm and Diagnostic Workstations. D.24.3 Alarm and Diagnostic Workstations Workstations shall consist of: D.24.3.1 A CPU, minimum 21 inch diagonal LCD monitor, keyboard and mouse. D.24.3.2 The default display shall be a simplified graphical diagram of the Radio System using icons that are color-coded to represent the current alarm status of each major component. D.24.3.3 Selecting an icon shall reveal the next level of system detail, allowing the user to then select another icon to drill down to the next level of detail, until the level of individual module or circuit board is reached. D.24.3.4 Alarms shall appear as flashing icons. D.24.4 Security D.24.4.1 D.24.4.2 May 17, 2012 Workstations shall be password-protected to prevent access by unauthorized individuals. Alarm and Diagnostic workstations shall not be physically placed in locations where access by persons not authorized to maintain the Radio System is unrestricted. Document 2 - Specification & Response Document Page 210 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.24 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.24 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Standard Standard Requirement Comply/ Section Exception D.24 D.24.1 D.24.1.1 D.24.1.2 D.24.1.3 D.24.1.4 D.24.1.5 D.24.1.6 D.24.1.7 D.24.1.8 D.24.2 D.24.2.1 D.24.2.1.1 D.24.2.2 D.24.2.2.1 D.24.2.2.2 D.24.2.2.3 D.24.2.2.4 D.24.2.2.5 D.24.2.2.6 D.24.2.3 D.24.3 D.24.3.1 D.24.3.2 D.24.3.3 D.24.3.4 D.24.4 D.24.4.1 D.24.4.2 {End Section D.24} May 17, 2012 Document 2 - Specification & Response Document Page 211 of 399 Maricopa County, Arizona D.25 12030-RFP P25 Radio System Infrastructure Upgrade System Administration Subsystem Functional & Technical Specifications The System Administration Subsystem shall provide: D.25.1 System Usage Reports The System Administration Subsystem shall collect and store data with regard to system usage. Data to be collected shall include but not be limited to the following: D.25.1.1 Error Event Log. D.25.1.2 Number of Push To Talk (“PTT”) requests per talkgroup per interval of time. D.25.1.3 Number of PTT grants per talkgroup per interval of time. D.25.1.4 Number of PTT requests per system per interval of time. D.25.1.5 Number of PTT grants per system per interval of time. D.25.1.6 Average number of calls in queue per interval of time. D.25.1.7 Maximum number of calls in queue per interval of time. D.25.1.8 Total number of calls queued per interval of time. D.25.1.9 Average length of queue delay. D.25.1.10 Maximum length of queue delay. D.25.1.11 Average PTT duration. D.25.1.12 Maximum PTT duration. D.25.1.13 Number of calls by type/interval. Call duration by type of call. D.25.1.14 Number of system busies per interval of time. D.25.1.15 Total busy time per interval of time. D.25.1.16 All control channel transactions. D.25.1.17 Additional information at the discretion of the Contractor. D.25.2 System Configuration Functions The System Administration Subsystem shall store and present data with regard to system configuration, and allow authorized users to change configurations and parameters. Data to be stored shall include but not be limited to the following: D.25.2.1 Configuration information for all components in the system. D.25.2.2 Functional configuration of controllers, channels and sites D.25.2.3 Control of trunking parameters including but not limited to: D.25.2.3.1 May 17, 2012 Channel Hang Time (message trunking) Document 2 - Specification & Response Document Page 212 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.25.2.3.2 Channel Fade Time (length of time a talkpath remains assigned without a valid transmission from the talkgroup) D.25.2.3.3 Emergency Call Time (length of channel hang time when an emergency call is initiated) D.25.3 Subscriber Radio Unit Management The System Administration Subsystem shall manage subscriber radio units. Management functions shall include but not be limited to the following: D.25.3.1 Manager database (list of system managers). D.25.3.2 Logged on managers. D.25.3.3 Regrouped radios. D.25.3.4 Inhibited radios. D.25.3.5 Storm plans. D.25.3.6 Commands (tasks)-in-Progress (regroups, inhibits). D.25.3.7 Database of authorized subscriber radio units, and the capability to add, delete and edit entries D.25.3.8 Database of subscriber configuration and attributes (by individual, talkgroup and multi-group), and the capability to add, delete and edit entries. D.25.4 Real-Time System and Talkgroup Usage Data The System Administration Subsystem shall collect and present real-time data with regard to system and talkgroup usage. Data to be collected shall include but not be limited to the following: D.25.4.1 Identification of calling units by talkgroup, PTT ID and PTT ID alias. D.25.4.2 Time of channel access. D.25.4.3 Duration of transmission. D.25.4.4 Classification of call. D.25.4.5 Talkpath assigned. D.25.4.6 Multicast site(s) or simulcast cells involved in a call. D.25.5 Selective Disablement of Field Units The System Administration Subsystem shall provide the selective disablement of individual subscriber radio units. D.25.5.1 May 17, 2012 Reactivation of disabled radios shall also be provided. Document 2 - Specification & Response Document Page 213 of 399 Maricopa County, Arizona D.25.6 Security D.25.6.1 D.25.6.2 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Access by the System Administration subsystem to the Radio System shall be locked down by both the computer MAC address and by user password authentication. System Administration workstations shall not be physically placed in locations where access by persons not authorized to administer the Radio System is unrestricted. Document 2 - Specification & Response Document Page 214 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.25 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.25 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.25 D.25.1 D.25.1.1 D.25.1.2 D.25.1.3 D.25.1.4 D.25.1.5 D.25.1.6 D.25.1.7 D.25.1.8 D.25.1.9 D.25.1.10 D.25.1.11 D.25.1.12 D.25.1.13 D.25.1.14 D.25.1.15 D.25.1.16 D.25.1.17 D.25.2 D.25.2.1 D.25.2.2 D.25.2.3 D.25.2.3.1 D.25.2.3.2 D.25.2.3.3 D.25.3 D.25.3.1 D.25.3.2 D.25.3.3 D.25.3.4 D.25.3.5 May 17, 2012 Document 2 - Specification & Response Document Page 215 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.25 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Standard Standard Requirement Comply/ Section Exception D.25.3.6 D.25.3.7 D.25.3.8 D.25.4 D.25.4.1 D.25.4.2 D.25.4.3 D.25.4.4 D.25.4.5 D.25.4.6 D.25.5 D.25.5.1 D.25.6 D.25.6.1 D.25.6.2 {End Section D.25} May 17, 2012 Document 2 - Specification & Response Document Page 216 of 399 Maricopa County, Arizona D.26 12030-RFP P25 Radio System Infrastructure Upgrade Electronic Security Systems The Contractor shall provide a Electronic Security Systems for each Site. D.26.1 Video Surveillance Each Site shall be equipped with video surveillance equipment. D.26.1.1 The video surveillance equipment shall be integrated with the County's existing video surveillance system. Information about the County's existing video surveillance system is contained in Document 3 Confidential Supplement. D.26.1.2 There shall be a minimum of two cameras per site; more for larger sites (Contractor to determine exact number). D.26.1.3 Cameras shall be suitable for outdoor use under the environmental conditions found at the Site. D.26.1.4 Cameras shall be placed in environmental housings to prevent damage and theft. D.26.2 Site Access Control Each Site shall be equipped with site access control equipment consisting of a proximity card reader and scramble keypad, electrically-operated locks on entry doors and intrusion detectors. D.26.2.1 The site access control equipment shall be integrated with the County's existing access control system. Information about the County's existing access control system is contained in Document 3 - Confidential Supplement. D.26.2.2 Doors shall also open with a key in the event of a failure of the Site Access Control System. D.26.2.2.1 May 17, 2012 Doors shall be keyed at the direction of the County. Document 2 - Specification & Response Document Page 217 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.26 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.26 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.26 D.26.1 D.26.1.1 D.26.1.2 D.26.1.3 D.26.1.4 D.26.2 D.26.2.1 D.26.2.2 D.26.2.2.1 {End Section D.26} May 17, 2012 Document 2 - Specification & Response Document Page 218 of 399 Maricopa County, Arizona D.27 12030-RFP P25 Radio System Infrastructure Upgrade Acceptance Testing Requirements Acceptance Testing shall be completed prior to Final Acceptance of the Radio System and the start of the Basic Warranty. Acceptance testing shall consist of six main phases which are described below: D.27.1 Pre-Installation (Factory) Acceptance Testing Prior to delivery to its final destination, the Contractor shall connect the Radio System and test it as an integrated whole at the Contractor’s facility to ensure that it meets all published specifications and the requirements of this document. D.27.1.1 At least two representatives of the County shall witness Pre-Installation Acceptance Testing. D.27.2 Component Acceptance Testing Following installation at its final destination, each component or piece of equipment shall be individually tested to ensure its compliance with manufacturer's published specifications and the requirements of this document. A complete list of components to be tested shall be developed during the Detailed Design process. D.27.2.1 May 17, 2012 The following information shall be recorded: D.27.2.1.1 The date, start time and end time of the test. D.27.2.1.2 The names and affiliations of persons performing and witnessing the test D.27.2.1.3 A diagram of the test setup D.27.2.1.4 The test equipment or measuring devices being employed D.27.2.1.5 The date of last calibration for each piece of test equipment or measuring device D.27.2.1.6 A detailed procedure for the test D.27.2.1.7 A complete and exact description of the results expected D.27 2.1.8 A complete and exact description of the actual results obtained D.27.2.1.9 A statement as to whether the results of the test met the criteria for success (“PASSED”) or did not meet the criteria for success (“FAILED”) D.27.2.1.10 The signatures of the authorized representatives of the County and the Contractor that supervised and witnessed the test Document 2 - Specification & Response Document Page 219 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.27.2.2 It is not necessary to perform Component Acceptance Tests all at once or near the completion of the Project. They may be performed immediately upon completion of construction or equipment installation at a Site, where the Component under test will interact with other Components at the Site, but not necessarily with Components at other Sites. D.27.2.3 Component Acceptance Testing shall be considered successfully completed if all individual components meet the stated specifications and requirements. D.27.2.4 In the event an individual component fails, that component shall be replaced at the Contractor's sole cost and expense and the test shall be repeated. D.27.3 Sub-System Acceptance Testing The purpose of Sub-System Testing is to determine whether each individual Subsystem functions in accordance with manufacturers' specifications and the requirements of this document, is acceptably reliable for inclusion in the System, was installed properly, and to document the initial state of each Subsystem to assist in troubleshooting future problems. D.27.3.1 D.27.3.2 May 17, 2012 Subsystems to be Tested The following is a preliminary list of Subsystems to be tested (complete list shall be developed during the Detailed Design process): D.27.3.1.1 Simulcast cells and multicast sites D.27.3.1.2 Key Management Facility and OTAR D.27.3.1.3 OTAP (if so equipped) D.27 3.1.4 Backhaul network D.27.3.1.5 Dispatch consoles D.27.3.1.6 Alarm and Diagnostic subsystem D.27.3.1.7 System Administration subsystem D.27.3.1.8 Site security subsystem D.27.3.1.9 Network security, including firewalls and intrusion detection devices and software The following information shall be recorded: D.27.3.2.1 The date, start time and end time of the test. D.27.3.2.2 The names and affiliations of persons performing and witnessing the test Document 2 - Specification & Response Document Page 220 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.27.3.2.3 A diagram of the test setup D.27.3.2.4 The test equipment or measuring devices being employed D.27.3.2.5 The date of last calibration for each piece of test equipment or measuring device D.27.3.2.6 A detailed procedure for the test D.27.3.2.7 A complete and exact description of the results expected D.27.3.2.8 A complete and exact description of the actual results obtained. D.27.3.2.9 A statement as to whether the results of the test met the criteria for success (“PASSED”) or did not meet the criteria for success (“FAILED”) D.27.3.2.10 The signatures of the authorized representatives of the County and the Contractor that supervised and witnessed the test D.27.3.3 It is not necessary to perform Subsystem Testing all at once at or near the completion of the Radio Project, although all Subsystem Tests must be performed and passed prior to the Ninety-Day Reliability Test. It is intended that, to the extent practical, Subsystem tests be performed as part of the normal Radio System optimization process D.27.3.4 Subsystem Acceptance Testing shall be considered successfully completed when it has been demonstrated: D.27.3.5 D.27.3.4.1 That all subsystems have been properly installed according to the manufacturer’s published instructions; the approved Final Design document, all applicable codes and standards and the best industry practices. D.27.3.4.2 That each feature or function of each subsystem operates properly and conforms to all manufacturers' specifications and the requirements of this document. In the event a subsystem component fails, the subsystem shall be repaired at the Contractor's sole cost and expense and the test shall be repeated. D.27.4 System Functional Acceptance Testing System Functional Acceptance Testing is the demonstration and documentation of the features and functions that will be available to end-users of the Radio System when the Radio System is fully installed and complete. May 17, 2012 Document 2 - Specification & Response Document Page 221 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.27.4.1 A complete list of features and functions to be tested shall be developed during the Detailed Design process. D.27.4.2 The following information shall be recorded: D.27.4.2.1 The feature or function being tested D.27 4.2.2 The date, start time and end time of the test. D.27.4.2.3 The names and affiliations of persons performing and witnessing the test D.27.4.2.4 A detailed procedure for the test D.27.4.2.5 A complete and exact description of the results expected and criteria for success D.27.4.2.6 A complete and exact description of the actual results obtained D.27.4.2.7 A statement as to whether the results of the test met the criteria for success (“PASSED”) or did not meet the criteria for success (“FAILED”) D.27.4.2.8 The signatures of the authorized representatives of the County and the Contractor that supervised and witnessed the test D.27.4.3 All System Functional Acceptance Testing shall be performed all at one time, immediately prior to the development of End-User training curriculum and course materials. D.27.4.4 System Functional Acceptance Testing shall be considered successfully completed when all end-user functions have (including Alarm and Diagnostic, System Administration and Security functions) have been demonstrated to function properly according to manufacturers' published specifications, the requirements of this document, and any additional features and functional specifications that may be defined during the Detailed Design process. D.27.5 Radio Coverage Verification Acceptance Testing The purpose of Radio Coverage Verification Acceptance Testing is to verify, to the greatest extent possible, that the geographic radio coverage provided by the installed and fully functioning Radio System equals or exceeds the geographic radio coverage and the reliability of that coverage that is guaranteed by the Contractor. D.27.5.1 May 17, 2012 Complete requirements and procedures for Radio Coverage Verification Acceptance Testing are contained in Appendix 6. Document 2 - Specification & Response Document Page 222 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.27.6 Ninety-Day Reliability Acceptance Test The purpose of the Ninety-Day Reliability Test is to determine whether the installed and fully functioning System is acceptably reliable for use by public safety first responders. D.27.6.1 May 17, 2012 Requirements and procedures for the Ninety-Day Reliability Test are contained in Appendix 7. Document 2 - Specification & Response Document Page 223 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.27 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.27 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.27 D.27.1 D.27.1.1 D.27.2 D.27.2.1 D.27.2.1.1 D.27.2.1.2 D.27.2.1.3 D.27.2.1.4 D.27.2.1.5 D.27.2.1.6 D.27.2.1.7 D.27.2.1.8 D.27.2.1.9 D.27.2.1.10 D.27.2.2 D.27.2.3 D.27.2.4 D.27.3 D.27.3.1 D.27.3.1.1 D.27.3.1.2 D.27.3.1.3 D.27.3.1.4 D.27.3.1.5 D.27.3.1.6 D.27.3.1.7 D.27.3.1.8 D.27.3.1.9 D.27.3.2 D.27.3.2.1 D.27.3.2.2 May 17, 2012 Document 2 - Specification & Response Document Page 224 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.27 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.27.3.2.3 D.27.3.2.4 D.27.3.2.5 D.27.3.2.6 D.27.3.2.7 D.27.3.2.8 D.27.3.2.9 D.27.3.2.10 D.27.3.3 D.27.3.4 D.27.3.4.1 D.27.3.4.2 D.27.3.5 D.27.4 D.27.4.1 D.27.4.2 D.27.4.2.1 D.27.4.2.2 D.27.4.2.3 D.27.4.2.4 D.27.4.2.5 D.27.4.2.6 D.27.4.2.7 D.27.4.2.8 D.27.4.3 D.27.4.4 D.27.5 D.27.5.1 D.27.6 D.27.6.1 {End Section D.27} May 17, 2012 Document 2 - Specification & Response Document Page 225 of 399 Maricopa County, Arizona D.28 12030-RFP P25 Radio System Infrastructure Upgrade Training Specifications The Contractor shall provide a comprehensive training program for end-users, system administration personnel, maintenance personnel and engineers, and County executives as described in this section. D.28.1 End-User Training The Contractor shall provide a comprehensive hands-on training program for end-users of mobile, portable and control station subscriber radios which shall be based upon a Train-the-Trainer approach. D.28.1.1 D.28.1.2 Participants will be deemed adequately trained if, after completing the prescribed training course, they can demonstrate: D.28.1.1.1 Consistently successful utilization of the functions of their assigned equipment as it is programmed for the new radio system, and; D.28.1.1.2 The ability to duplicate the training sessions and successfully train their own personnel. Training topics shall include but not be limited to: D.28.1.2.1 Overview of the new system D.28.1.2.2 Area of operation; radio coverage provided D.28.1.2.3 Comparison of old and new systems D.28.1.2.4 Operation of all features and functions of their assigned equipment, including selection of all available talkgroups and channels D.28.1.2.5 Proper use of all associated accessories D.28.1.2.6 Proper radio procedures and etiquette D.28.1.2.7 Procedures for interoperability D.28.1.3 End-user training shall have a customized curriculum and materials that correspond to the individual user group's radio programming, operational procedures and interoperability procedures. D.28.1.4 Training materials shall include a printed course guide, a Trainer's Handbook, video and /or PowerPoint presentations and pocket sized, laminated, water resistant quick reference card describing features and programming in an abbreviated format. D.28.2 Dispatcher Training The Contractor shall provide a comprehensive hands-on training program for users of dispatch equipment which shall based upon a Train-the-Trainer approach. May 17, 2012 Document 2 - Specification & Response Document Page 226 of 399 Maricopa County, Arizona D.28.2.1 D.28.2.2 12030-RFP P25 Radio System Infrastructure Upgrade Participants will be deemed adequately trained if, after completing the prescribed training course, they can demonstrate: D.28.2.1.1 Consistently successful utilization of the functions of their assigned equipment as it is programmed for the new radio system, and; D.28.2.1.2 The ability to duplicate the training sessions and successfully train their own personnel. Training topics shall include but not be limited to: D.28.2.2.1 Overview of the new system D.28.2.2.2 Area of operation; radio coverage provided D.28.2.2.3 Comparison of old and new systems D.28.2.2.4 Operation of all dispatch features D.28.2.2.5 Equipment failure modes and procedures to maintain communications until the failure is repaired D.28.2.2.6 Operation and control of backup control stations D.28.2.2.7 Procedures for interoperability D.28.2.3 Dispatcher training shall have a customized curriculum and materials that correspond to the individual user group's dispatch console programming, operational procedures and interoperability procedures. D.28.2.4 Training materials shall include a printed course guide, a Trainer's Handbook, video and /or Power point presentations and pocket sized, laminated, water resistant quick reference cards describing features and programming in an abbreviated format. D.28.3 Training for Maintenance Personnel and System Administrators The Contractor shall provide a number of specialized courses over a broad spectrum of topics for the County's in-house staff of radio programmers, technicians, engineers, system administrators, installers, help desk staff and technical management staff. D.28.3.1 May 17, 2012 Training topics shall include but not be limited to: D.28.3.1.1 Overview of the new system D.28.3.1.2 Area of operation; radio coverage provided D.28.3.1.3 Comparison of old and new systems D.28.3.1.4 Features and programming of portable, mobile and control station subscriber equipment D.28.3.1.5 Subscriber equipment troubleshooting and repair Document 2 - Specification & Response Document Page 227 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.28.3.1.6 Subscriber equipment installation techniques D.28.3.1.7 Principles of digital radio systems D.28.3.1.8 Introduction to Ethernet, Internet Protocol and MPLS D.28.3.1.9 Trunked radio infrastructure equipment familiarization D.28.3.1.10 Trunked radio infrastructure equipment configuration, preventive maintenance, failure modes, troubleshooting and repair D.28.3.1.11 Backhaul network equipment familiarization D.28.3.1.12 Backhaul network equipment configuration, preventive maintenance failure modes, troubleshooting and repair D.28.3.1.13 Operation of the Alarm and Diagnostic subsystem D.28.3.1.14 Training on key individual components used in the Radio System D.28.3.1.15 System administration: management of the subscriber radio fleet, radio ID databases, assignment and management of system features and functions D.28.3.2 The training shall have a customized curriculum and materials that correspond to the new radio infrastructure equipment, subscriber equipment, backhaul network and system management equipment. D.28.3.3 The technical training shall include substantial hands-on involvement of County staff in the actual installation, optimization and implementation of the new Radio System. D.28.3.4 Training materials shall include a printed course guides, video and /or PowerPoint presentations, block diagrams, schematic diagrams and circuit descriptions, technical and maintenance manuals for individual system components and quick reference cards describing key information and short-cuts to speed troubleshooting and repair. D.28.3.5 Technical training is expected to occur at multiple times during the course of the Radio System implementation process. Training given later in the process shall contain updates on technical changes and advancements that may have occurred since the previous training. D.28.3.6 The County will permit members of its staff to attend the same class more than once, if refresher training is deemed necessary by the County. Document 2 - Specification & Response Document Page 228 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.28.4 Executive and Management Familiarization This training session shall provide an overview of the new system that will give decision makers, policy makers and emergency management planners a working knowledge of radio system operations. D.28.4.1 D.28.4.2 The training sessions shall include, at a minimum, the following topics: D.28.4.1.1 Overview of the new system D.28.4.1.2 Area of operation; radio coverage provided D.28.4.1.3 Comparison of old and new systems D.28.4.1.4 Interoperability considerations Training materials shall include a printed course guide, video and/or PowerPoint presentations. D.28.5 Source Materials The Contractor shall provide the original source files for all training materials in Microsoft Word, Microsoft PowerPoint or Adobe Acrobat format to the County, so the County may produce its own customized training materials for future training sessions. D.28.5.1 Instructions on the use of the source materials to produce customized training materials shall be provided. D.28.5.2 Source materials shall be organized and presented so that they are easy to use. D.28.6 Training Locations Due to restrictions on travel for County employees, all training classes shall be given in Maricopa County, with the exact location or venue to be specified by the County. D.28.7 Early Delivery of Certain Training Classes D.28.7.1 Prior to installation of any equipment that will require significant planning for its initial configuration (including but not limited to dispatch consoles, Master Network Switch and subscriber radio equipment), a configuration training session shall be provided to the County employees and other individuals that are responsible for planning the initial configuration of the dispatch equipment. D.28.7.2 The first session of training in any category shall be a "pilot" session given to supervisory or management-level employees of the agencies involved. D.28.7.2.1 Any deficiencies noted in the training program shall be corrected prior to the start of any remaining sessions. D.28.8 Scheduling of Training D.28.8.1 Training sessions shall be scheduled at the direction of the County. May 17, 2012 Document 2 - Specification & Response Document Page 229 of 399 Maricopa County, Arizona D.28.8.2 May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade The County may require training classes to be scheduled to coincide with work shifts other than 8am to 5pm, Monday through Friday. Document 2 - Specification & Response Document Page 230 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.28 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.28 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.28 D.28.1 D.28.1.1 D.28.1.1.1 D.28.1.1.2 D.28.1.2 D.28.1.2.1 D.28.1.2.2 D.28.1.2.3 D.28.1.2.4 D.28.1.2.5 D.28.1.2.6 D.28.1.2.7 D.28.1.3 D.28.1.4 D.28.2 D.28.2.1 D.28.2.1.1 D.28.2.1.2 D.28.2.2 D.28.2.2.1 D.28.2.2.2 D.28.2.2.3 D.28.2.2.4 D.28.2.2.5 D.28.2.2.6 D.28.2.2.7 D.28.2.3 D.28.2.4 D.28.3 D.28.3.1 D.28.3.1.1 May 17, 2012 Document 2 - Specification & Response Document Page 231 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.28 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Standard Standard Requirement Comply/ Section Exception D.28.3.1.2 D.28.3.1.3 D.28.3.1.4 D.28.3.1.5 D.28.3.1.6 D.28.3.1.7 D.28.3.1.8 D.28.3.1.9 D.28.3.1.10 D.28.3.1.11 D.28.3.1.12 D.28.3.1.13 D.28.3.1.14 D.28.3.1.15 D.28.3.2 D.28.3.3 D.28.3.4 D.28.3.5 D.28.3.6 D.28.4 D.28.4.1 D.28.4.1.1 D.28.4.1.2 D.28.4.1.3 D.28.4.1.4 D.28.4.2 D.28.5 D.28.5.1 D.28.5.2 D.28.6 D.28.7 D.28.7.1 D.28.7.2 May 17, 2012 Document 2 - Specification & Response Document Page 232 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.28 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Standard Standard Requirement Comply/ Section Exception D.28.7.2.1 D.28.8 D.28.8.1 D.28.8.2 {End Section D.28} May 17, 2012 Document 2 - Specification & Response Document Page 233 of 399 Maricopa County, Arizona D.29 12030-RFP P25 Radio System Infrastructure Upgrade Requirements for Commissioning, Migration and Decommissioning D.29.1 Single End-User User Cutover From the perspective of the end-user, there shall be a single cutover date and time where use of the new Radio System infrastructure will begin and use of the old radio infrastructure will be discontinued ("End-User Cutover"). D.29.1.1 From the perspective of the Contractor and the County's Project staff, many "cutover points" shall be permitted after the successful completion of the End-User Cutover where new Antenna Sites and other equipment and features come on line. However, these shall be done in a manner that offers no burden or inconvenience to the endusers. D.29.2 No Manual Roaming With the exception of a short period (24 hours or less) during the End-User Cutover, there shall be no requirement for end-users to change their channel selector or make any other manual adjustment to their subscriber radio equipment in order to roam throughout the Radio System coverage area. D.29.3 Cutover Rollback Plan D.29.3.1 The New Radio System shall operate concurrently with the old radio system for as long as is necessary to ensure that the new Radio System is stable and reliable. D.29.3.2 The Contractor shall have a comprehensive plan to roll back to the old radio system in the event problems with the new Radio System occur that are of such magnitude that it becomes unreliable for day-to-day use by the end users. D.29.3.3 The old radio system infrastructure shall remain fully functional and kept in a "hot-standby" mode for a minimum of ninety calendar days following the successful completion of the End-User Cutover, ready to be returned to service immediately in the event problems with the new Radio System occur that are of such magnitude that the end-users must roll back to the old radio system. D.29.3.4 Subscriber radio equipment shall remain programmed to operate on the old radio system for a period of ninety calendar days (or longer, if necessary) following the successful completion of the End-User Cutover. D.29 4 Project Schedule Shall Be Based on Cutover Requirements The schedule and work plan for the entire Project shall be based on these requirements for Commissioning, Migration and De-Commissioning. May 17, 2012 Document 2 - Specification & Response Document Page 234 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.29 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.29 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.29 D.29.1 D.29.1.1 D.29.2 D.29.3 D.29.3.1 D.29.3.2 D.29.3.3 D.29.3.4 D.29.4 {End Section D.29} May 17, 2012 Document 2 - Specification & Response Document Page 235 of 399 Maricopa County, Arizona D.30 12030-RFP P25 Radio System Infrastructure Upgrade Archive Documents Archive Documents shall be provided in sufficient detail so that a competent radio maintenance technician may use them to maintain the Radio System and a competent engineer may use them to design future enhancements to the Radio System. At a minimum, the Contractor shall provide the following Archive Documents: D.30.1 Construction Drawings A complete set of drawings derived from the original site construction drawings modified to correctly document the actual construction of site facilities and the installation of all ancillary equipment ("As-Built Construction Drawings"). D.30.1.1 Drawings that are merely "red-lined" to indicate changes to the original design shall not be acceptable. The drawings shall be modified to become new original drawings that reflect the actual construction. D.30.2 Materials List A final list of all materials and equipment provided as part of this Project. D.30.3 Block Diagrams and Schematic Diagrams Block diagrams and schematic diagrams showing the actual installation and cabling of all electronic components and cabling down to the connector pin-out level. D.30.3.1 Each block diagram and schematic diagram shall be accompanied by a narrative describing how each component is connected and operates within the Radio System. D.30.4 Operating and Maintenance Manuals A minimum of ten copies of all operating and maintenance manuals shall be provided for all equipment, components and test equipment purchased for the Radio System. D.30.5 Acceptance Test Documentation Documents describing each Acceptance Test performed and the results of each test. D.30.6 Training Materials A minimum of three copies of all materials provided for training. D.30.7 Software Copies of all installed software provided under this Contract shall be provided to the County. D.30.7.1 Software copies shall be provided on CD-ROM, DVD-ROM, or other convenient archival format. D.30.7.2 Software serial numbers and installation keys shall be provided to the County along with each software copy. D.30.7.3 A complete list of passwords in use for all installed software shall be provided to the County. D.30.8 Document Formats Documents shall be provided in electronic formats: May 17, 2012 Document 2 - Specification & Response Document Page 236 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade D.30.8.1 Construction drawings shall be provided in AutoCAD format (latest revision at the time of document delivery). D.30.8.2 The Materials List shall be provided in Microsoft Excel format (latest revision at the time of document delivery). D.30.8.3 Block diagrams and schematic diagrams shall be provided in Microsoft Visio format (latest revision at the time of document delivery). Written descriptions shall be provided in Microsoft Word or Adobe Acrobat format (latest revision at the time of document delivery). D.30.8.4 Operating and maintenance manuals shall be provided in Adobe Acrobat format. D.30.8.5 Acceptance test documentation shall be provided in Adobe Acrobat format. D.30.8.6 Training materials shall be provided in the format(s) in which they were originally developed. Document 2 - Specification & Response Document Page 237 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.30 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.30 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.30 D.30.1 D.30.1.1 D.30.2 D.30.3 D.30.3.1 D.30.4 D.30.5 D.30.6 D.30.7 D.30.7.1 D.30.7.2 D.30.7.3 D.30.8 D.30.8.1 D.30.8.2 D.30.8.3 D.30.8.4 D.30.8.5 D.30.8.6 {End Section D.30} May 17, 2012 Document 2 - Specification & Response Document Page 238 of 399 Maricopa County, Arizona D.31 12030-RFP P25 Radio System Infrastructure Upgrade Warranties D.31.1 Basic Warranty The Contractor shall warrant that all equipment, materials and work complies with the requirements of this RFP and shall be free of defects for a period of one year from the date of Final Acceptance of the Project. The Contractor shall troubleshoot, maintain and repair the Radio System at no additional cost to the County for the duration of the warranty term ("Basic Warranty"). D.31.2 In addition to the Basic Warranty, the Contractor shall troubleshoot, maintain and repair, at no additional cost to the County, any portion(s) of the legacy radio system that is kept and re-used as part of the new Radio System ("Legacy System Interim Warranty"). The Legacy System Interim Warranty shall begin at the moment the portion of the legacy radio system is physically incorporated into the new Radio System and shall expire upon Final Acceptance of the Project. Upon Final Acceptance of the Project, the entire Radio System, both the legacy portion(s) and new portion, shall be covered by the Basic Warranty. In the case of site physical plant (building, tower, HVAC, generators and alarms), the requirements of the Legacy System Warranty shall apply only to those physical plant items that the Contractor has repaired, upgraded or replaced. D.31.3 In addition to the Basic Warranty and the Legacy System Interim Warranty, the Contractor shall troubleshoot, maintain and repair, at no additional cost to the County, any portion of the Radio System, new or legacy, that is placed into normal, everyday use by the County prior to Final Acceptance of the Project ("Beneficial Use Interim Warranty"). The Beneficial Use Interim Warranty shall begin at the moment the portion of the Radio System is placed into normal, everyday use by the County and shall expire upon Final Acceptance of the Project. Upon Final Acceptance of the Project, the entire Radio System, including all portions that were previously placed into normal, everyday service by the County, shall be covered by the Basic Warranty. D.31.4 The Basic Warranty, the Legacy System Interim Warranty and the Beneficial Use Interim Warranty shall include but not be limited to the following: D.31.4.1 Software Maintenance and Repair in the same manner as described in Section D.32.1 Requirements for Optional Post-Warranty Maintenance and Repair Services, Software Maintenance and Repair. D.31.4.1.1 It is the intent of the County to have the entire Radio System equipped with the latest software revision at the expiration of the Basic Warranty period. D.31.5 Response time for calls for Warranty service from the County shall be the same as described in Section D.32.3 Requirements for Optional Post-Warranty Maintenance and Repair Services, Complete Troubleshooting and Repair of the Radio System. May 17, 2012 Document 2 - Specification & Response Document Page 239 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section D.31 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.31 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.31 D.31.1 D.31.2 D.31.3 D.31.4 D.31.4.1 D.31.4.1.1 D.31.5 {End Section D.31} May 17, 2012 Document 2 - Specification & Response Document Page 240 of 399 Maricopa County, Arizona D.32 12030-RFP P25 Radio System Infrastructure Upgrade Requirements for Optional Post-Warranty Maintenance and Repair Services D.32.1 Software Maintenance and Repair The Contractor shall provide labor and materials to maintain and repair software as described in this Section. D.32.1.1 D.32.1.2 May 17, 2012 The software to be maintained and repaired shall include but not necessarily be limited to: D.32.1.1.1 Master Network Switch software. D.32.1.1.2 Redundant Master Network Switch software. D.32.1.1.3 Software contained within Network Components such as switches and routers. D.32.1.1.4 Software and firmware contained within RF devices such as transmitters and receivers. D.32.1.1.5 Software contained within the System Management and Alarm and Diagnostic subsystems. D.32.1.1.6 Software and firmware within subscriber radios that are affected by a change in any of the above components. D.32.1.1.7 All other software and firmware that are affected by a change in any of the above components. D.32.1.1.8 Software to be maintained shall include operating systems and device drivers. D.32.1.1.9 Software to be maintained shall include configuration and initialization files. D.32.1.1.10 Anti-malware software versions and malware databases shall be kept current at all times. Maintenance services shall include, but not be limited to: D.32.1.2.1 Routine updating of software and firmware to the latest revision. D.32.1.2.2 "Bug" fixes. D.32.1.2.3 Repairs of latent defects. D.32.1.2.4 Restoration of malfunctioning software D.32.1.2.5 The services of software designers and programmers when needed on an emergency basis to restore the Radio System to normal operation. Document 2 - Specification & Response Document Page 241 of 399 Maricopa County, Arizona D.32.1.3 12030-RFP P25 Radio System Infrastructure Upgrade Response by the Contractor D.32.1.3.1 Routine updates of software and firmware shall be scheduled at the convenience of the County. D.32.1.3.2 Routine updates of software shall be thoroughly planned prior to the event, including a plan to roll back the software to the last known working version in the event of unforeseen problems. D.32.1.3.3 Bugs and latent defects shall be repaired promptly upon reporting of the bug or latent defect to the Contractor. D.32.1.3.4 The Contractor shall provide the County with a 24hour/7 day per week telephone number to report software malfunctions. D.32.1.3.5 The Contractor shall respond to a report of malfunctioning software and have restoration efforts underway within one hour. D.32.1.3.6 The Contractor shall have a planned escalation of expert support personnel. If a resolution to the reported problem is not found within two hours, the problem will be escalated to the next tier of expertise. D.32.2 Depot Repair of Field Replaceable Units ("FRUs") The Contractor shall maintain a local stock of all FRUs potentially needed to repair the Radio System. The local stock of FRUs shall be sufficient to repair 95 percent of all common failures of Radio System equipment and components. May 17, 2012 D.32.2.1 When a failed FRU is reported to the Contractor, a fully tested and guaranteed fully functional replacement FRU shall be removed from local stock and used to replace the failed FRU. D.32.2.2 The failed FRU shall be shipped to the Contractor's repair depot where it will be repaired or replaced. D.32.2.3 A fully tested and guaranteed fully functional new or refurbished FRU shall be placed in local stock to replace the FRU that was removed. D.32.2.4 The local stock shall be available to maintenance personnel, whether they are employees of the Contractor or of the County, on a 24 hour per day/7 day per week basis. D.32.2.5 The term "Field Replaceable Unit" shall be construed to mean: D.32.2.5.1 An electronic module, or D.32.2.5.2 An individual circuit board, or Document 2 - Specification & Response Document Page 242 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.2.5.3 An entire device that is more quickly or economically repaired by completely replacing it than by replacing individual modules, circuit boards or circuit components on-site. Such devices shall include, but not be limited to: D.32.2.5.3.1 LAN switches D.32.2.5.3.2 Routers D.32.2.6 Refurbished FRUs shall meet all manufacturers' specifications for new FRUs. D.32.2.7 The Respondent/Contractor shall provide a list of all FRUs and quantities necessary to repair 95% of all common failures of Radio System equipment and components. D.32.3 Complete Troubleshooting and Repair of the Radio System The Contractor shall provide labor and materials to troubleshoot and repair the Radio System electronic systems (excluding subscriber radios) in the field in response to calls for service from the County. D.32.3.1 The Contractor shall maintain a local staff of service and maintenance personnel of sufficient size and expertise to respond to all calls for service from the County in compliance with this specification. D.32.3.2 The Contractor shall provide a 24 hour/7 day per week telephone number for the County to place calls for service. D.32.3.2.1 D.32.3.3 The County shall provide the Contractor with a list of individuals that are authorized to call the Contractor for service on behalf of the County. D.32.3.4 Response by the Contractor The Contractor shall respond to calls for service from the County within a pre-determined time period, depending on the severity of the problem reported. D.32.3.4.1 May 17, 2012 In addition to the telephone number, the Contractor may offer an Internet-based means for the County to place calls for service. For service calls classified as "major," the Contractor's service personnel shall respond by telephone within fifteen minutes, shall begin restoration efforts within one hour, shall be on-site (if required) within two hours for locations within the Greater Phoenix area, three hours for sites outside of the Greater Phoenix area. and six hours or one hour after sunrise, whichever is greater, for helicopter-access-only sites. The reported Document 2 - Specification & Response Document Page 243 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade problem shall be resolved and the Radio System returned to normal operation within eight hours of the placement of the call for service by the County. D.32.3.5 May 17, 2012 D.32.3.4.2 For service calls classified as "minor," the Contractor's service personnel shall respond by telephone within four hours or, if the call for service is reported after 6:00 PM, the beginning of the next calendar day. The Contractor shall begin restoration efforts within two hours of the telephone response to the County, and shall be on-site (if required) within six hours of the telephone response to the County. The reported problem shall be resolved and the Radio System returned to normal operation within twenty-four hours of the placement of the call for service by the County. D.32.3.4.3 Failure to respond to a service call, begin restoration efforts or arrive on-site within the specified time frames shall result in monetary penalties to the Contractor. D.32.3.4.4 The Contractor shall have additional levels of support available from factory service technicians and engineers that shall be available in the event that resolution of the reported problem and return to normal operation takes longer than the time frames specified. D.32.3.4.5 The Contractor shall have a planned escalation of expert support personnel. If a resolution to the reported problem is not found within the specified time frame, the problem will be automatically escalated to the next tier of expertise. D.32.3.4.6 In the case of a "major" service call, the maximum length of time permitted to elapse before normal operation is restored shall be 24 hours. Failure to meet this goal shall result in monetary penalties to the Contractor. Classification of Calls for Service D.32.3.5.1 A "major" call for service is one that has caused or, if not promptly repaired has the potential to cause, a significant disruption of service to the end users of the radio system. Service calls that shall be classified as "major" include but are not limited to: Document 2 - Specification & Response Document Page 244 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.3.5.2 May 17, 2012 D.32.3.5.1.1 Failure of the Master Network Switch or Redundant Master Network Switch even if failover to the other has occurred and the disruption to end users has not occurred. D.32.3.5.1.2 A failure that causes a simulcast cell or multicast site to revert to site trunking or failsoft. D.32.3.5.1.3 Failure of twenty percent or more of dispatch consoles at any individual dispatch center. D.32.3.5.1.4 Backhaul system failure resulting in a path switch or reversion to standby equipment D.32.3.5.1.5 Complete failure of any antenna site D.32.3.5.1.6 Loss of 30 percent or more of talkpaths at any antenna site. D.32.3.5.1.7 Failure of UPS at any Radio System infrastructure site. D.32.3.5.1.8 Logging Recorder failure D.32.3.5.1.9 Loss of fifty percent or more of Alarm and Diagnostic subsystem workstations D.32.3.5.1.10 Complete failure of environmental control systems at any site A "minor" call for service is one that has caused or, if not promptly repaired, a loss of traffic capacity to the end users of the radio system or a loss in the ability of maintenance personnel to detect and restore system faults. Service calls that shall be classified as "minor" include but are not limited to: D.32.3.5.2.1 Failure of a single transmitter or receiver at any site D.32.3.5.2.2 Failure of less than fifty percent of Alarm and Diagnostic subsystem workstations. D.32.3.5.2.3 Failure of a single dispatch console at any individual dispatch center Document 2 - Specification & Response Document Page 245 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.3.5.3 D.32.3.5.2.4 Failure of a single environmental control system at any site where there are redundant environmental control systems D.32.3.5.2.5 Any component or module failure which results in loss of less than 30 percent of the talkpaths at any antenna site Reclassification of Service Calls Due to Emergencies The County shall have the absolute right, unilaterally and at its sole discretion, to re-classify any service call as "major" in the event that the County is involved in an emergency situation involving the protection of the life, safety or property of the general public and the failure presents a potential hazard to the general public or employees of the County. D.32.4 Remote Monitoring of the Radio System by the Contractor The Contractor shall provide labor and materials to remotely monitor the health and status of the Radio System and all its equipment and components on a 24 hour/7 day per week basis, and initiate responses as described in Section D.32.3 without the need for placement of a call for service by the County. D.32.4.1 The costs for remote monitoring of the Radio System, including but not limited to leased telecommunications circuits and additional network security required by the remote monitoring arrangement shall be borne solely by the Contractor. D.32.4.2 The County may also report calls for service to the Contractor. All requirements of Section D.32.3 shall apply to calls for service placed by the County. D.32.5 Preventive Maintenance Program for Radio System Electronic Systems The Contractor shall provide labor and materials to provide a program of preventive maintenance to the electronic systems that are part of the Radio System. The Preventive Maintenance program shall consist of periodic inspections and repairs: D.32.5.1 Annually D.32.5.1.1 D.32.5.1.2 May 17, 2012 Verify transmitter power output, modulation parameters and frequency accuracy and adjust, repair or replace as necessary. Verify receiver sensitivity, interference rejection and frequency accuracy and adjust, repair or replace as necessary. Document 2 - Specification & Response Document Page 246 of 399 Maricopa County, Arizona D.32.5.2 12030-RFP P25 Radio System Infrastructure Upgrade D.32.5.1.3 Verify that mechanisms to switch over to redundant components function properly. D.32.5.1.4 Remove dust and dirt that may have accumulated on equipment and surfaces. D.32.5.1.5 Inspect all cables and connectors for damage or deterioration and repair or replace as necessary. D.32.5.1.6 Inspect and check condition of batteries and replace deteriorated cells if necessary. Semi-Annually D.32.5.2.1 Check tuning of transmitter combiners and RF filter components and adjust if necessary. D.32.5.2.2 Perform sweeps of antenna systems in the frequency and time domains and repair or replace if necessary. D.32.5.2.3 Check tower-top amplifiers for proper gain and the absence of intermodulation products and adjust, repair or replace as necessary. D.32.5.2.4 Stress-test the backhaul network to ensure that the specified design bandwidth and capacity is available, and adjust, repair or replace components as necessary. D.32.6 Depot Repair of Subscriber Radio Equipment by the Contractor The Contractor shall provide labor and materials to repair failed subscriber radio equipment (mobile radios, portable radios and control stations). D.32.6.1 The Contractor shall provide a shipping address where the County shall send failed subscriber radio equipment for repair. D.32.6.1.1 D.32.6.2 Upon receipt of a failed subscriber radio unit, the Contractor shall proceed to repair the unit in an efficient and timely manner. D.32.6.3 Upon completion of the repair(s), the Contractor shall ship the repaired unit(s) back to the County. D.32.6.3.1 May 17, 2012 The County shall pay the cost of shipping failed units to the Contractor, or, the Contractor may optionally offer pre-paid shipping of failed units to the Contractor's depot. The Contractor shall pay the cost of shipping repaired unit(s) back to the County. Document 2 - Specification & Response Document Page 247 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.6.4 Average turnaround time between the receipt of a failed subscriber radio unit by the Contractor and the shipment of the same repaired unit back to the County shall be five business days. D.32.6.5 Maximum turnaround time between the receipt of a failed subscriber radio unit by the Contractor and the shipment of the same repaired unit back to the County shall be ten business days. D.32.6.6 Failure to meet the turnaround times specified above shall result in monetary penalties to the Contractor. D.32.6.7 The depot repair service described above shall include electronic failures and physical damage to housings, displays, circuit boards, controls and connectors. D.32.6.8 The depot repair services described above may be priced as a monthly charge per covered subscriber radio, a flat rate per repaired subscriber radio, or a combination of both methods. D.32.6.9 Subscriber radio equipment that is deemed uneconomical to repair shall be immediately returned to the County. D.32.6.10 The Contractor shall track each individual subscriber radio unit from the moment of receipt at the depot to the moment of shipment back to the County. D.32.6.10.1 A monthly report of units received, units repaired (including the repairs made), and units shipped shall be provided to the County. D.32.7 Field Service of Mobile Subscribers The Contractor shall provide both drive-up service and field location service. D.32.7.1 May 17, 2012 Drive-Up Service The Contractor shall specify a minimum of one shop location (more than one shop location is preferred) within Maricopa County where vehicles may be taken for service of mobile subscriber radios. D.32.7.1.1 The shop(s) shall maintain a stock of the parts needed to repair the most common failures of the type(s) of mobile subscriber radios used by the County. D.32.7.1.2 Qualified service technicians will troubleshoot the subscriber radio and, if possible, immediately repair it. D.32.7.1.3 If the subscriber radio is not immediately repairable, it will be removed from service and repaired as quickly as possible. Document 2 - Specification & Response Document Page 248 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.7.1.4 D.32.7.2 May 17, 2012 Upon repair of the subscriber radio, the County will be notified to bring the vehicle back to the shop location, where the subscriber radio will be re-installed and tested for proper operation. Field Location Service Upon receipt of a call for service from the County, the Contractor shall dispatch a service vehicle and qualified service technician to the location of the failed mobile subscriber radio. D.32.7.2.1 The service vehicle(s) shall maintain a stock of the parts needed to repair the most common failures of the type(s) of mobile subscriber radios used by the County. D.32.7.2.2 The service technician shall troubleshoot the subscriber radio and, if possible, immediately repair it. D.32.7.2.3 If the subscriber radio is not immediately repairable, it shall be removed from service, taken back to the shop and repaired as quickly as possible. D.32.7.2.4 Upon repair of the subscriber radio, the County shall be notified, and an appointment shall be made to return the subscriber radio to the vehicle. D.32.7.2.5 At the appointed date and time, the service vehicle and service technician shall return to the location of the failed mobile subscriber radio, where the subscriber radio shall be re-installed and tested for proper operation. D.32.7.3 Average turnaround time between the removal from service of a failed subscriber radio unit by the Contractor and the notification to the County that the subscriber radio has been repaired shall be five business days. D.32.7.4 Maximum turnaround time between the removal from service of a failed subscriber radio unit by the Contractor and the notification to the County that the subscriber radio has been repaired shall be ten business days. D.32.7.5 Failure to meet the turnaround times specified above shall result in monetary penalties to the Contractor. D.32.7.6 Subscriber radio equipment that is deemed uneconomical to repair shall be immediately returned to the County. Document 2 - Specification & Response Document Page 249 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.7.7 The depot repair service described above shall include electronic failures and physical damage to housings, displays, circuit boards, controls and connectors. D.32.7.8 The Contractor shall track each individual subscriber radio unit from the moment of removal from service to the moment of return to the original vehicle. D.32.7.8.1 D.32.7.9 A monthly report of units received, units repaired (including the repairs made), and units returned shall be provided to the County. The services described above may be priced as a monthly charge per covered subscriber radio, a flat rate per repaired subscriber radio, or a combination of both methods. D.32.8 Field Service of Control Station Subscribers Upon receipt of a call for service from the County, the Contractor shall dispatch a service vehicle and qualified service technician to the location of the failed control station subscriber radio. May 17, 2012 D.32.8.1 The service vehicle(s) shall maintain a stock of the parts needed to repair the most common failures of the type(s) of control station subscriber radios used by the County. D.32.8.2 The service technician shall troubleshoot the subscriber radio and, if possible, immediately repair it. D.32.8.3 If the subscriber radio is not immediately repairable, it shall be removed from service, taken back to the shop and repaired as quickly as possible. D.32.8.4 Upon repair of the subscriber radio, the County shall be notified, and an appointment shall be made to return the subscriber radio to its original location. D.32.8.5 At the appointed date and time, the service vehicle and service technician shall return to the location of the failed control station subscriber radio, where the subscriber radio shall be re-installed and tested for proper operation. D.32.8.6 Average turnaround time between the removal from service of a failed subscriber radio unit by the Contractor and the notification to the County that the subscriber radio has been repaired shall be five business days. D.32.8.7 Maximum turnaround time between the removal from service of a failed subscriber radio unit by the Contractor and the notification to the Document 2 - Specification & Response Document Page 250 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade County that the subscriber radio has been repaired shall be ten business days. D.32.8.8 Failure to meet the turnaround times specified above shall result in monetary penalties to the Contractor. D.32.8.9 Subscriber radio equipment that is deemed uneconomical to repair shall be immediately returned to the County. D.32.8.10 The service described above shall include electronic failures and physical damage to housings, displays, circuit boards, controls and connectors. D.32.8.11 The Contractor shall track each individual subscriber radio unit from the moment of removal from service to the moment of return to the original location. D.32.8.11.1 D.32.8.12 A monthly report of units received, units repaired (including the repairs made), and units returned shall be provided to the County. The depot repair services described above may be priced as a monthly charge per covered subscriber radio, a flat rate per repaired subscriber radio, or a combination of both methods. D.32.9 Factory Technical and Engineering Support In the event the County elects to self-maintain some or all of the Radio System electronic systems, there will be a need from time to time for support from factory technicians and engineers. The Contractor shall provide this support on an as-needed basis. There shall be three levels of support: D.32.9.1 Remote Support County engineers and technicians shall have access to the Contractor's experts via telephone or e-mail at any time during normal business hours, 8:00 AM through 5:00 PM, Arizona time, Monday through Friday. D.32.9.2 Emergency Remote Support The Contractor shall ensure that the Contractor's experts are available on a 24 hour/7 day per week basis in the event of an emergency. D.32.9.2.1 D.32.9.3 May 17, 2012 The Contractor's expert(s) shall respond by telephone to emergency calls for assistance from the County within two hours. Emergency On-Site Support The Contractor shall make its experts available for emergency on-site support, if needed. Document 2 - Specification & Response Document Page 251 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.9.3.1 D.32.9.4 The Contractor's expert(s) shall arrive in Maricopa County, ready to work, within 24 hours of the placement of a request for Emergency On-Site Support by the County. Technical and Engineering Documents The Contractor shall make available to the County any of its technical and engineering documents necessary to assist the County in the troubleshooting and repair of the failure being reported. D.32.9.4.1 In the case of remote support, documents may be emailed to the County's engineers and technicians. D.32.10 Purchase of Replacement Parts, Components and Accessories In the event the County elects to self-maintain some or all of the Radio System electronic systems, there will be a need from time to time for the County to purchase replacement parts, components and accessories. The Contractor shall make its entire catalog of replacement parts, components and accessories available for purchase at discounted or "wholesale" prices. D.32.10.1 The Respondent/Contractor shall specify a list of recommended spare parts and components that should be kept on hand to repair a minimum of 90 percent of the most common Radio System infrastructure failures. D.32.11 Physical Plant Maintenance The Contractor shall provide labor and materials to maintain physical plant equipment and components at all antenna sites and other equipment locations. Physical plant equipment shall include but not be limited to: D.32.11.1 D.32.11.2 May 17, 2012 Environmental Conditioning Systems D.32.11.1.1 Environmental conditioning systems include air conditioners, heaters, heat pumps and ventilation fans. D.32.11.1.2 The Contractor shall inspect each environmental conditioning system every six months and shall clean or replace filters, replace worn or aging parts and make any repairs needed at the time of inspection. D.32.11.1.3 The Contractor shall repair environmental conditioning systems in response to calls for service from the County. D.32.11.1.4 The Contractor shall respond to calls for service from the County within two hours and shall begin on-site restoration efforts within six hours. Backup Generators D.32.11.2.1 The Contractor shall inspect each backup generator every six months and shall change oil and other fluids Document 2 - Specification & Response Document Page 252 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade (excluding fuel), clean or replace filters, replace worn or aging parts and make any repairs needed at the time of inspection. D.32.11.3 D.32.11.4 D.32.11.2.2 The Contractor shall repair backup generators in response to calls for service from the County. D.32.11.2.3 The Contractor shall respond to calls for service from the County within two hours and shall begin on-site restoration efforts within six hours. Antenna Support Structures D.32.11.3.1 Antenna support structures include towers, monopoles and frames used to mount Radio System antennas. D.32.11.3.2 The Contractor shall inspect each antenna support structure every three years and shall check bolts for tightness and re-tighten if necessary, inspect structural components for deformation and rust and replace if necessary, check tower lighting systems and replace bulbs and perform repairs if necessary, inspect concrete foundations for deterioration and repair if necessary, and make any other repairs necessary at the time of inspection. D.32.11.3.3 The Contractor shall replace failed tower light bulbs and repair or replace failed tower lighting systems within 24 hours of notification of such failure by the County. D.32.11.3.4 If the antenna support structure is painted to comply with FAA requirements, the Contractor shall re-paint the antenna support structure every ten years, or earlier if the paint has deteriorated prematurely. Uninterruptible Power Supplies D.32.11.4.1 The Contractor shall inspect each UPS system annually and check all voltage levels, electrical connections and battery conditions and replace defective cells and make any other repairs or adjustments needed at the time of inspection. D.32.11.4.2 May 17, 2012 The Contractor shall troubleshoot and repair UPS backup systems in response to calls for service from the County. Document 2 - Specification & Response Document Page 253 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade D.32.11.4.3 The Contractor shall respond to calls for service from the County within two hours and shall begin on-site restoration efforts within six hours. Section D.32 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.32 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.32 D.32.1 D.32.1.1 D.32.1.1.1 D.32.1.1.2 D.32.1.1.3 D.32.1.1.4 D.32.1.1.5 D.32.1.1.6 D.32.1.1.7 D.32.1.1.8 D.32.1.1.9 D.32.1.1.10 D.32.1.2 D.32.1.2.1 D.32.1.2.2 D.32.1.2.3 D.32.1.2.4 D.32.1.2.5 D.32.1.3 D.32.1.3.1 D.32.1.3.2 D.32.1.3.3 D.32.1.3.4 D.32.1.3.5 D.32.1.3.6 D.32.2 D.32.2.1 May 17, 2012 Document 2 - Specification & Response Document Page 254 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.32 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.32.2.2 D.32.2.3 D.32.2.4 D.32.2.5 D.32.2.5.1 D.32.2.5.2 D.32.2.5.3 D.32.2.5.3.1 D.32.2.5.3.2 D.32.2.6 D.32.2.7 D.32.3 D.32.3.1 D.32.3.2 D.32.3.2.1 D.32.3.3 D.32.3.4 D.32.3.4.1 D.32.3.4.2 D.32.3.4.3 D.32.3.4.4 D.32.3.4.5 D.32.3.4.6 D.32.3.5 D.32.3.5.1 D.32.3.5.1.1 D.32.3.5.1.2 D.32.3.5.1.3 D.32.3.5.1.4 D.32.3.5.1.5 D.32.3.5.1.6 D.32.3.5.1.7 D.32.3.5.1.8 May 17, 2012 Document 2 - Specification & Response Document Page 255 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.32 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.32.3.5.1.9 D.32.3.5.1.10 D.32.3.5.2 D.32.3.5.2.1 D.32.3.5.2.2 D.32.3.5.2.3 D.32.3.5.2.4 D.32.3.5.2.5 D.32.3.5.3 D.32.4 D.32.4.1 D.32.4.2 D.32.5 D.32.5.1 D.32.5.1.1 D.32.5.1.2 D.32.5.1.3 D.32.5.1.4 D.32.5.1.5 D.32.5.1.6 D.32.5.2 D.32.5.2.1 D.32.5.2.2 D.32.5.2.3 D.32.5.2.4 D.32.6 D.32.6.1 D.32.6.1.1 D.32.6.2 D.32.6.3 D.32.6.3.1 D.32.6.4 D.32.6.5 May 17, 2012 Document 2 - Specification & Response Document Page 256 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.32 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section Exception D.32.6.6 D.32.6.7 D.32.6.8 D.32.6.9 D.32.6.10 D.32.6.10.1 D.32.7 D.32.7.1 D.32.7.1.1 D.32.7.1.2 D.32.7.1.3 D.32.7.1.4 D.32.7.2 D.32.7.2.1 D.32.7.2.2 D.32.7.2.3 D.32.7.2.4 D.32.7.2.5 D.32.7.3 D.32.7.4 D.32.7.5 D.32.7.6 D.32.7.7 D.32.7.8 D.32.7.8.1 D.32.7.9 D.32.8 D.32.8.1 D.32.8.2 D.32.8.3 D.32.8.4 D.32.8.5 D.32.8.6 May 17, 2012 Document 2 - Specification & Response Document Page 257 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.32 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Comply Comply Comply Standard Standard Standard Comply Comply Comply Comply Standard Standard Standard Standard Requirement Comply/ Section Exception D.32.8.7 D.32.8.8 D.32.8.9 D.32.8.10 D.32.8.11 D.32.8.11.1 D.32.8.12 D.32.9 D.32.9.1 D.32.9.2 D.32.9.2.1 D.32.9.3 D.32.9.3.1 D.32.9.4 D.32.9.4.1 D.32.10 D.32.10.1 D.32.11 D.32.11.1 D.32.11.1.1 D.32.11.1.2 D.32.11.1.3 D.32.11.1.4 D.32.11.2 D.32.11.2.1 D.32.11.2.2 D.32.11.2.3 D.32.11.3 D.32.11.3.1 D.32.11.3.2 D.32.11.3.3 D.32.11.3.4 D.32.11.4 May 17, 2012 Document 2 - Specification & Response Document Page 258 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section D.32 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Standard Standard Standard Requirement Comply/ Section Exception D.32.11.4.1 D.32.11.4.2 D.32.11.4.3 {End Section D.32} May 17, 2012 Document 2 - Specification & Response Document Page 259 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SECTION E - SUBSCRIBER RADIO EQUIPMENT TECHNICAL & FUNCTIONAL SPECIFICATIONS E.1 Multiband Subscribers The word "multiband" shall mean that the subscriber radio is equipped to operate in the 700 MHz/800 MHz band (for the purposes of this Section D, the 700 MHz band and the 800 MHz band shall be considered a single frequency band) and one or more of the following frequency bands: May 17, 2012 E.1.1 450 MHz to 512 MHz ("UHF band") E.1.2 150 MHz to 174 MHz ("High VHF band") E.1.3 30 MHz to 50 MHz ("Low VHF band") Document 2 - Specification & Response Document Page 260 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications RFP Section: 12030-RFP, Document 2, Section E.1 No Response Required {End Section E.1} May 17, 2012 Document 2 - Specification & Response Document Page 261 of 399 Maricopa County, Arizona E.2 12030-RFP P25 Radio System Infrastructure Upgrade General Requirements for All Subscribers E.2.1 Modes of Operation All Subscribers shall be equipped to operate in the following modes: E.2.1.1 Project 25 Phase 2 (TDMA) trunked E.2.1.2 Project 25 Phase 1 (FDMA) trunked E.2.1.3 Project 25 FDMA conventional E.2.1.4 E.2.2 E.2.1.3.1 Simplex (direct mode) E.2.1.3.2 Half-duplex (repeater mode) Analog conventional, including the following sub-modes: E.2.1.4.1 Carrier squelch mode E.2.1.4.2 Continuous Tone-Coded Squelch ("CTCSS") mode on transmit, receive or both E.2.1.4.3 Continuous Digital-Coded Squelch ("CDCSS") mode on transmit, receive or both E.2.1.4.4 Simplex (direct mode) E.2.1.4.5 Half-duplex (repeater mode) E.2.1.5 There shall be no restriction on the order or grouping of modes programmed into subscriber radios. For example, it shall not be acceptable to require all conventional channels to be grouped together in one bank of channels or "zone." E.2.1.6 In the case of multiband Subscribers, there shall be no restriction on the order or grouping of frequency bands. For example, it shall not be acceptable to require all VHF High band channels to be grouped together in one bank of channels or "zone." Talkgroup and Channel Selection E.2.2.1 All Subscribers shall be equipped with a minimum of 512 separate talkgroups and conventional channels. E.2.2.1.1 E.2.2.2 May 17, 2012 Channels and talkgroups shall be divided into banks, or "zones," of sixteen. Subscribers shall be equipped with: E.2.2.2.1 A sixteen-position channel selector, and E.2.2.2.2 A zone selector. E.2.2.2.3 Positions on the channel selector shall be identified numerically from one to sixteen. Document 2 - Specification & Response Document Page 262 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.2.2.2.4 E.2.2.3 Zones shall be identified using characters of the alphabet, beginning with "A." If the Subscriber is equipped with an alphanumeric display, the Subscriber shall be equipped to select the desired talkgroup or channel by scrolling through the entire list of talkgroups and channels alphabetically by talkgroup or channel name. E.2.2.3.1 A means shall be provided for the user to jump quickly through the list by selecting the first letter of the talkgroup or channel name. For example, a user would begin the alphabetic search for the talkgroup named "MCSO East" by first selecting the letter "M." E.2.3 Special-Purpose Subscribers Modes of Operation Certain Subscribers used for special purposes (example: a control station used to permanently monitor a single channel or talkgroup) shall not be required to operate in all the modes specified above. E.2.4 Frequency Band (Single-Band Subscribers) All Subscribers shall operate in the 700MHz/800 MHz band. E.2.4.1 E.2.5 Subscriber radios shall be equipped to be programmed on any authorized channel center frequency. Frequency Band (Multi-Band Subscribers) Certain subscriber radios shall be equipped to operate in both the 700 MHz/800 MHz band and the VHF High Band. E.2.5.1 Subscriber radios shall be equipped to be programmed on any authorized channel center frequency. E.2.6 Push-To-Talk Identification All Subscribers shall transmit a unique ID upon activation of PTT ("PTT ID") which shall be received and displayed on the dispatchers' screens and on the receiving subscriber radios' local displays (if the receiving radio is so equipped). E.2.7 Seamless Roaming All subscribers shall be equipped for seamless roaming over the entire coverage area of the radio system. E.2.7.1 May 17, 2012 When roaming, Subscribers shall maintain affiliation and communications with the talkgroup selected by the user without manual intervention (except that certain talkgroups may be prohibited from affiliation with certain sites as determined by the programming of the talkgroup or the individual Subscriber). Document 2 - Specification & Response Document Page 263 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.2.8 Out-Of Range Notification Subscribers shall emit an audible and a visual warning when unable to receive or transmit a signal of sufficient quality to maintain connection/affiliation with the Radio System infrastructure. E.2.9 Fallback Mode In the event of a malfunction of the Radio System infrastructure that places the infrastructure in a fallback or "failsoft" mode, Subscribers shall: E.2.9.1 Emit an audible and visual warning alerting the user of the fallback mode of operation. E.2.9.2 Scan for a simulcast cell or multicast site with acceptable signal quality that is not in the fallback mode. If found, the Subscriber shall affiliate with the new site or cell. E.2.9.3 If an acceptable site or cell is not found, the Subscriber shall place itself in a fallback mode compatible with the cell or site that has placed itself in the fallback mode. Communications shall continue to the extent possible in the fallback mode. E.2.9.4 While in fallback mode, the subscriber shall continue to scan for an acceptable site or cell that is not in the fallback mode. If found, the Subscriber shall affiliate with the new site or cell. E.2.9.5 Upon return of the affected infrastructure to normal trunked operation, the Subscriber shall automatically revert back to normal trunked operation. E.2.10 Site Trunking Mode In the event of a malfunction of the Radio System infrastructure that places the infrastructure in a "site trunking" mode, Subscribers shall: E.2.10.1 Emit an audible and visual warning alerting the user of the degraded mode of operation. E.2.11 Selective Disablement of Subscribers Upon receipt of the proper command from the Radio System infrastructure, the Subscriber shall completely mute its audio output and become unresponsive to user input. May 17, 2012 E.2.11.1 If so equipped, the Subscriber shall transmit its current GPS location. E.2.11.2 The receiver shall remain active, listening for a command from the radio infrastructure to return to normal operation. E.2.11.3 Upon receipt of the proper command, the Subscriber shall return to normal operation. Document 2 - Specification & Response Document Page 264 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.2.12 Individual Unit Alert and Individual Call All Subscribers shall be equipped to receive Individual Unit Alerts and participate in Individual Calls initiated by others. See Sections D.21.6.4 and D.21.6.5. E.2.12.1 Selected Subscribers shall be equipped to initiate Individual Unit Alerts and Individual Calls to other Subscribers. E.2.13 Scan and Priority Scan All Subscribers shall be equipped to scan multiple talkgroups and conventional channels. E.2.13.1 Subscribers shall be equipped to allow the user to manually define at least one (1) scan list and to add or delete channels and talkgroups from the list as desired. E.2.13.2 Maximum size of any scan list shall be a minimum of ten talkgroups and channels. E.2.13.3 Certain Subscribers shall be equipped with a Priority Scan feature, in which a message from a higher priority talkgroup or channel will override lower priority messages in progress. E.2.14 Optional Over-the-Air Programming At the discretion of the County, the County may require that all subscribers shall be equipped for Over-the-Air Programming of the radio personality and feature set ("OTAP"). May 17, 2012 Document 2 - Specification & Response Document Page 265 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section E.2 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section E.2 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section/ Exception Subsection E.2 E.2.1 E.2.1.1 E.2.1.2 E.2.1.3 E.2.1.3.1 E.2.1.3.2 E.2.1.4 E.2.1.4.1 E.2.1.4.2 E.2.1.4.3 E.2.1.4.4 E.2.1.4.5 E.2.1.5 E.2.1.6 E.2.2 E.2.2.1 E.2.2.1.1 E.2.2.2 E.2.2.2.1 E.2.2.2.2 E.2.2.2.3 E.2.2.2.4 E.2.2.3 E.2.2.3.1 E.2.3 E.2.4 E.2.4.1 E.2.5 E.2.5.1 E.2.6 E.2.7 May 17, 2012 Document 2 - Specification & Response Document Page 266 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section E.2 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section/ Exception Subsection E.2.7.1 E.2.8 E.2.9 E.2.9.1 E.2.9.2 E.2.9.3 E.2.9.4 E.2.9.5 E.2.10 E.2.10.1 E.2.11 E.2.11.1 E.2.11.2 E.2.11.3 E.2.12 E.2.12.1 E.2.13 E.2.13.1 E.2.13.2 E.2.13.3 E.2.14 {End Section E.2} May 17, 2012 Document 2 - Specification & Response Document Page 267 of 399 Maricopa County, Arizona E.3 12030-RFP P25 Radio System Infrastructure Upgrade Encryption Certain subscriber radio equipment shall be equipped to transmit and receive encrypted communications ("encrypted subscribers"). E.3.1 Encryption type shall be 256-bit AES, compliant with National Institute of Standards and Technology publication FIPS-197 (latest revision). E.3.1.1 E.3.2 Cryptographic modules shall comply with the requirements for Security Level 1 specified in National Institute of Standards and Technology publication FIPS-140-2. The selection of clear or encrypted communications shall also be slaved to the channel selection mechanism. The correct encryption key shall be selected upon selection of the desired talkgroup or channel. E.3.2.1 A front-panel switch shall be provided that allows the user to manually select clear or encrypted communication for the channel or talkgroup they are currently affiliated with. E.3.2.2 The setting of the manual encrypted/clear selector switch shall have no effect unless it is used after the desired channel or talkgroup has been selected. E.3.3 Encrypted subscribers shall be equipped to use multiple encryption keys. E.3.4 Encrypted subscribers shall be equipped with Over-the-Air-Rekeying ("OTAR") of encryption keys. E.3.5 Encrypted subscribers shall be equipped to receive encryption keys via a KVL. May 17, 2012 Document 2 - Specification & Response Document Page 268 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section E.3 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: 12030-RFP, Document 2, Section E.3 Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Requirement Comply/ Section/ Exception Subsection E.3 E.3.1 E.3.1.1 E.3.2 E.3.2.1 E.3.2.2 E.3.3 E.3.4 E.3.5 {End Section E.3} May 17, 2012 Document 2 - Specification & Response Document Page 269 of 399 Maricopa County, Arizona E.4 12030-RFP P25 Radio System Infrastructure Upgrade Requirements for Portable Subscriber Radio Equipment Portable subscriber radio equipment ("portables") shall be provided. E.4.1 Requirements Common to All Portables E.4.1.1 All portables shall be equipped with an emergency button. E.4.1.1.1 The emergency button shall be located in an easy-tofind spot on the portable, yet be protected from inadvertent activation. E.4.1.1.2 The emergency button shall be colored red or orange. E.4.1.1.3 Upon activation of the emergency button, the portable shall transmit its PTT ID and an emergency signal that will be received by the dispatcher and by other Subscribers tuned to the same channel or talkgroup. E.4.1.1.4 If so equipped, the portable shall transmit its GPS location upon activation of the emergency button. E.4.1.2 Portables shall be as small, lightweight and rugged as possible. E.4.1.3 Removal of the battery or opening of the battery compartment shall not cause the integrity of the radio against environmental conditions to be degraded in any way. E.4.1.4 The on/off volume control knob and the channel selector knob shall be large and uniquely identifiable by touch, even when the user is wearing gloves. E.4.1.5 All portables shall have a side connector for attachment of remote speaker-microphones and a separate audio output connector for attachment of surveillance earpieces and other accessories. E.4.1.5.1 E.4.1.6 May 17, 2012 All connectors shall be protected from dust, dirt and moisture when not in use. All portables shall have a wide range of optional accessories that shall include, but not be limited to: E.4.1.6.1 Remote speaker-microphones E.4.1.6.2 Surveillance earpieces E.4.1.6.3 Combination noise-cancelling headphone and noisecancelling microphone for use in tactical situations E.4.1.6.4 Carrying holsters, carrying straps and chest packs E.4.1.6.5 High capacity batteries Document 2 - Specification & Response Document Page 270 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.4.1.6.6 Clamshell-type battery packs for use with off-the-shelf alkaline or lithium batteries E.4.1.6.7 Single-unit chargers in standard-charge, rapid-charge and battery conditioning configurations E.4.1.6.8 Multi-unit chargers in standard-charge, rapid-charge and battery conditioning configurations E.4.1.6.9 Multi-colored housings and/or escutcheons for easy and quick identification of individual portable subscribers. E.4.1.6.9.1 E.4.2 Types of Portables E.4.2.1 Type A Portable Type A portables shall have the following characteristics: E.4.2.1.1 They shall be the manufacturer's high-tier product. E.4.2.1.2 They shall be an encrypted subscriber. E.4.2.1.3 They shall be equipped to pass the following MIL-STD810F environmental test procedures: E.4.2.1.4 May 17, 2012 A glow-in-the-dark or highly reflective housing or escutcheon is desired for operation in low-light conditions. E.4.2.1.3.1 Low Pressure 500.4/1 E.4.2.1.3.2 High Temperature 501.4/1 & 2 E.4.2.1.3.3 Low Temperature 502.4/1 & 2 E.4.2.1.3.4 Temperature Shock 503.4/1 E.4.2.1.3.5 Solar Radiation 505.4/2 E.4.2.1.3.6 Blowing Rain 506.4/1 E.4.2.1.3.7 Humidity 507.4/2 E.4.2.1.3.8 Salt Fog 509.4 E.4.2.1.3.9 Blowing Dust 510.4/1 E.4.2.1.3.10 Immersion 512.4/1 E.4.2.1.3.11 Vibration 514.5/1 E.4.2.1.3.12 Shock (Functional/Basic) 516.5/1 E.4.2.1.3.13 Shock (Transit Drop) 516.5/4 They shall be equipped with a backlit graphical full-color front-panel display which shall display a minimum of 32 Document 2 - Specification & Response Document Page 271 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade alphanumeric characters, plus graphical indicators of battery charge level and received signal strength. E.4.2.1.5 May 17, 2012 They shall be equipped with a backlit top-panel alphanumeric display of a minimum of sixteen characters that displays the currently selected talkgroup or channel name. E.4.2.1.5.1 The top-panel alphanumeric display shall be viewable by the user when the portable is worn in a holster on the hip. E.4.2.1.5.2 The display backlighting shall change to red when the portable is out of range of the infrastructure, or the infrastructure is in failsoft or site trunking modes. E.4.2.1.6 They shall be equipped with a twelve-button numeric keypad, plus additional buttons as required for the selection of talkgroups, channels and zones. E.4.2.1.7 They shall have a minimum of two configurable (via the programming of the individual Subscriber) switches on the top panel and three configurable buttons on the side panel(s). E.4.2.1.8 They shall be equipped with noise suppression circuitry to ensure high intelligibility when transmitting from a high noise environment. E.4.2.1.9 They shall be equipped to transmit their GPS location upon the following events, which shall be configurable via the programming of the individual subscriber: E.4.2.1.9.1 Upon every PTT. E.4.2.1.9.2 Upon activation of the emergency button. E.4.2.1.9.3 Upon receipt of the proper command from the Radio System infrastructure. E.4.2.1.10 They shall transmit with a maximum power of no less than 2.5 Watts. E.4.2.1.11 They shall have a low-power mode with a maximum transmit power of no greater than one Watt. The selection of low-power mode shall be slaved to the channel selection mechanism. The high power or low Document 2 - Specification & Response Document Page 272 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade power mode shall be automatically selected upon selection of the desired talkgroup or channel. E.4.2.1.12 Batteries E.4.2.1.12.1 E.4.2.1.12.2 E.4.2.3 May 17, 2012 Optional batteries shall be available with larger capacities. E.4.2.1.13 They shall be optionally available with Factory Mutual Intrinsically Safe certification. E.4.2.1.14 They shall be capable of initiation of Individual Alerts and Individual Calls to a specific list of other Subscribers. E.4.2.1.15 E.4.2.2 The standard battery supplied with the radio shall be sufficient to operate the radio for a minimum of twelve hours with a duty cycle of 5% transmit, 5% receive, 90% idle ("5/5/90 duty cycle"). E.4.2.1.14.1 The list shall be able to hold at least sixty-four (64) individual PTT ID's. E.4.2.1.14.2 The list shall be independently userprogrammable for each subscriber radio so equipped. They shall be equipped with the Priority Scan feature. Type B Portable The Type B Portable shall have the same features as the Type A Portable except: E.4.2.2.1 The Type B Portable shall be multiband, operating in both the 700 MHz/800 MHz band and the VHF High Band. E.4.2.2.2 In the VHF High Band, the transmit power output shall be no less than 5 Watts. Type C Portable The Type C Portable shall have the following characteristics: E.4.2.3.1 They shall be a "middle-tier" product. E.4.2.3.2 They shall be equipped to pass the following MIL-STD810F environmental test procedures: E.4.2.3.2.1 Low Pressure 500.4/1 E.4.2.3.2.2 High Temperature 501.4/1 & 2 Document 2 - Specification & Response Document Page 273 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade E.4.2.3.2.3 Low Temperature 502.4/1 & 2 E.4.2.3.2.4 Temperature Shock 503.4/1 E.4.2.3.2.5 Solar Radiation 505.4/2 E.4.2.3.2.6 Blowing Rain 506.4/1 E.4.2.3.2.7 Humidity 507.4/2 E.4.2.3.2.8 Salt Fog 509.4 E.4.2.3.2.9 Blowing Dust 510.4/1 E.4.2.3.2.10 Immersion 512.4/1 E.4.2.3.2.11 Vibration 514.5/1 E.4.2.3.2.12 Shock (Functional/Basic) 516.5/1 E.4.2.3.2.13 Shock (Transit Drop) 516.5/4 E.4.2.3.3 They shall be equipped with a backlit front-panel display which shall display a minimum of 16 alphanumeric characters, plus graphical indicators of battery charge level and received signal strength. E.4.2.3.4 They shall be equipped with a twelve-button numeric keypad, plus additional buttons as required for the selection of talkgroups, channels and zones. E.4.2.3.5 They shall have a minimum of two configurable (via the programming of the individual Subscriber) switches on the top panel and three configurable buttons on the side panel(s). E.4.2.3.6 They shall transmit with a maximum power of no less than 2.5 Watts. E.4.2.3.7 They shall have a low-power mode with a maximum transmit power of no greater than one Watt. The selection of low-power mode shall be slaved to the channel selection mechanism. The high power or low power mode shall be automatically selected upon selection of the desired talkgroup or channel. E.4.2.3.8 Batteries E.4.2.3.8.1 The standard battery supplied with the radio shall be sufficient to operate the radio for a minimum of twelve hours with a duty cycle of 5% transmit, 5% receive, 90% idle ("5/5/90 duty cycle"). Document 2 - Specification & Response Document Page 274 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.4.2.3.8.2 E.4.2.3.9 Type C Portables shall be optionally available with Factory Mutual Intrinsically Safe certification. E.4.2.3.10 Type C Portables shall be capable of initiation of Individual Alerts and Individual Calls to a specific list of other Subscribers. E.4.2.3.11 E.4.2.4 E.4.2.3.10.1 The list shall be able to hold at least sixty-four (64) individual PTT ID's. E.4.2.3.10.2 The list shall be independently userprogrammable for each subscriber radio so equipped. They shall be equipped with the Priority Scan feature. Type D Portable E.4.2.4.1 They shall be a "middle-tier" product. E.4.2.4.2 E.4.2.4.3 May 17, 2012 Optional batteries shall be available with larger capacities. They shall be equipped to pass the following MIL-STD810F environmental test procedures: E.4.2.4.2.1 Low Pressure 500.4/1 E.4.2.4.2.2 High Temperature 501.4/1 & 2 E.4.2.4.2.3 Low Temperature 502.4/1 & 2 E.4.2.4.2.4 Temperature Shock 503.4/1 E.4.2.4.2.5 Solar Radiation 505.4/2 E.4.2.4.2.6 Blowing Rain 506.4/1 E.4.2.4.2.7 Humidity 507.4/2 E.4.2.4.2.8 Salt Fog 509.4 E.4.2.4.2.9 Blowing Dust 510.4/1 E.4.2.4.2.10 Immersion 512.4/1 E.4.2.4.2.11 Vibration 514.5/1 E.4.2.4.2.12 Shock (Functional/Basic) 516.5/1 E.4.2.4.2.13 Shock (Transit Drop) 516.5/4 They shall be equipped with a backlit front-panel display which shall display a minimum of 16 alphanumeric characters, plus graphical indicators of battery charge level and received signal strength. Document 2 - Specification & Response Document Page 275 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.4.2.4.4 They shall be equipped with front-panel buttons as required for the selection of talkgroups, channels and zones. E.4.2.4.5 They shall have a minimum of two configurable (via the programming of the individual Subscriber) switches on the top panel and three configurable buttons on the side panel(s). E.4.2.4.6 They shall transmit with a maximum power of no less than 2.5 Watts. E.4.2.4.7 Batteries E.4.2.4.7.1 E.4.2.4.7.2 May 17, 2012 The standard battery supplied with the radio shall be sufficient to operate the radio for a minimum of eight hours with a duty cycle of 5% transmit, 5% receive, 90% idle ("5/5/90 duty cycle"). Optional batteries shall be available with larger capacities. Document 2 - Specification & Response Document Page 276 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section E.4 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.4 E.4.1 E.4.1.1 E.4.1.1.1 E.4.1.1.2 E.4.1.1.3 E.4.1.1.4 E.4.1.2 E.4.1.3 E.4.1.4 E.4.1.5 E.4.1.5.1 E.4.1.6 E.4.1.6.1 E.4.1.6.2 E.4.1.6.3 E.4.1.6.4 E.4.1.6.5 E.4.1.6.6 E.4.1.6.7 E.4.1.6.8 E.4.1.6.9 E.4.1.6.9.1 E.4.2 E.4.2.1 E.4.2.1.1 E.4.2.1.2 E.4.2.1.3 E.4.2.1.3.1 E.4.2.1.3.2 E.4.2.1.3.3 E.4.2.1.3.4 May 17, 2012 12030-RFP, Document 2, Section E.4 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Document 2 - Specification & Response Document Page 277 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.4.2.1.3.5 E.4.2.1.3.6 E.4.2.1.3.7 E.4.2.1.3.8 E.4.2.1.3.9 E.4.2.1.3.10 E.4.2.1.3.11 E.4.2.1.3.12 E.4.2.1.3.13 E.4.2.1.4 E.4.2.1.5 E.4.2.1.5.1 E.4.2.1.5.2 E.4.2.1.6 E.4.2.1.7 E.4.2.1.8 E.4.2.1.9 E.4.2.1.9.1 E.4.2.1.9.2 E.4.2.1.9.3 E.4.2.1.10 E.4.2.1.11 E.4.2.1.12 E.4.2.1.12.1 E.4.2.1.12.2 E.4.2.1.13 E.4.2.1.14 E.4.2.1.14.1 E.4.2.1.14.2 E.4.2.1.15 E.4.2.2 E.4.2.2.1 E.4.2.2.2 May 17, 2012 12030-RFP, Document 2, Section E.4 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Document 2 - Specification & Response Document Page 278 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.4.2.3 E.4.2.3.1 E.4.2.3.2 E.4.2.3.2.1 E.4.2.3.2.2 E.4.2.3.2.3 E.4.2.3.2.4 E.4.2.3.2.5 E.4.2.3.2.6 E.4.2.3.2.7 E.4.2.3.2.8 E.4.2.3.2.9 E.4.2.3.2.10 E.4.2.3.2.11 E.4.2.3.2.12 E.4.2.3.2.13 E.4.2.3.3 E.4.2.3.4 E.4.2.3.5 E.4.2.3.6 E.4.2.3.7 E.4.2.3.8 E.4.2.3.8.1 E.4.2.3.8.2 E.4.2.3.9 E.4.2.3.10 E.4.2.3.10.1 E.4.2.3.10.2 E.4.2.3.11 E.4.2.4 E.4.2.4.1 E.4.2.4.2 E.4.2.4.2.1 May 17, 2012 12030-RFP, Document 2, Section E.4 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Document 2 - Specification & Response Document Page 279 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.4.2.4.2.2 E.4.2.4.2.3 E.4.2.4.2.4 E.4.2.4.2.5 E.4.2.4.2.6 E.4.2.4.2.7 E.4.2.4.2.8 E.4.2.4.2.9 E.4.2.4.2.10 E.4.2.4.2.11 E.4.2.4.2.12 E.4.2.4.2.13 E.4.2.4.3 E.4.2.4.4 E.4.2.4.5 E.4.2.4.6 E.4.2.4.7 E.4.2.4.7.1 E.4.2.4.7.2 12030-RFP, Document 2, Section E.4 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Standard Standard {End Section E.4} May 17, 2012 Document 2 - Specification & Response Document Page 280 of 399 Maricopa County, Arizona E.5 12030-RFP P25 Radio System Infrastructure Upgrade Requirements for Mobile Subscriber Radio Equipment Mobile subscriber radio equipment ("mobiles") shall be provided. E.5.1 Requirements Common to All Mobiles E.5.1.1 All mobiles shall be equipped with an emergency button. E.5.1.1.1 The emergency button shall be located in an easy-tofind spot on the mobile, yet be protected from inadvertent activation. E.5.1.1.2 The emergency button shall be colored red or orange. E.5.1.1.3 Upon activation of the emergency button, the mobile shall transmit its PTT ID and an emergency signal that will be received by the dispatcher and by other Subscribers tuned to the same channel or talkgroup. E.5.1.1.4 If so equipped, the mobile shall transmit its GPS location upon activation of the emergency button. E.5.1.2 Mobiles shall be as small, lightweight and rugged as possible. E.5.1.3 Mobiles shall be delivered complete with power cables, external speaker, microphone and antenna. E.5.1.4 Audio output shall be a minimum of ten Watts. E.5.1.5 Maximum transmitter RF power output shall be 35 Watts for the 700 MHz/800 MHz frequency band. E.5.1.5.1 E.5.1.6 E.5.1.7 Mobiles shall be equipped to operate from a +13.8 Volt (nominal) negative-ground power source. E.5.1.6.1 For installations in vehicles with other than 13.8 Volt negative-ground power source, the Contractor shall provide and install an appropriate DC to DC converter. E.5.1.6.2 Mobiles shall incorporate protective circuitry to prevent damage from voltage transients and reversed polarity. The default mobile antenna shall be a quarter-wave, unity gain antenna using a 3/4 inch "NMO" style mount, and shall include a minimum of seventeen feet of low-loss coaxial cable and a low-loss RF connector to match the mobile RF connector. E.5.1.7.1 May 17, 2012 For multiband mobiles, the maximum transmitter RF output for all other bands shall be 50 Watts. Multiband mobiles shall also include additional antennas as specified above which correspond to the additional frequency band(s). Document 2 - Specification & Response Document Page 281 of 399 Maricopa County, Arizona E.5.1.8 E.5.1.9 12030-RFP P25 Radio System Infrastructure Upgrade The following antennas may be purchased as an option: E.5.1.8.1 760 MHz to 870 MHz low-profile antenna with black molded ABS radome and 3/4 inch NMO-style mount, including a minimum of seventeen feet of low-loss coaxial cable and a low-loss RF connector to match the mobile RF connector, Laird Technologies TRAB7603 or approved equal. E.5.1.8.2 760 MHz to 870 MHz on-glass disguise antenna designed to look like a cellular telephone antenna, 3dB gain, including a minimum of seventeen feet of low-loss coaxial cable with low-loss connector to match the mobile RF connector. Mobiles shall have two basic configurations: E.5.1.9.1 E.5.1.9.2 E.5.1.10 E.5.2 May 17, 2012 "Remote-mount" mobiles shall have a separate transceiver package and control head. E.5.1.9.1.1 Remote-mount mobiles shall come complete with interconnecting cables. E.5.1.9.1.2 Remote-mount mobiles may have one, two or more fully-functional control heads connected to one transceiver package. "Dash-mount" mobiles shall have the control head integrated with the transceiver package. A contact closure output shall be provided that shall activate upon reception of an Individual Alert. The contact closure shall be suitable for driving a relay or other device to honk the vehicle horn or flash the lights. Types of Mobiles E.5.2.1 Type E Mobile Type E mobiles shall have the following characteristics: E.5.2.1.1 They shall be the manufacturer's high-tier product. E.5.2.1.2 They shall be an encrypted subscriber. E.5.2.1.3 They shall be equipped to pass the following MIL-STD810G environmental test procedures: E.5.2.1.3.1 Low Pressure 500.5/1 & 2 E.5.2.1.3.2 High Temperature 501.5/1 & 2 Document 2 - Specification & Response Document Page 282 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.5.2.1.4 E.5.2.1.3.3 Low Temperature 502.5/1 & 2 E.5.2.1.3.4 Temperature Shock 503.5/1 E.5.2.1.3.5 Solar Radiation 505.5/2 E.5.2.1.3.6 Blowing Rain 506.5/1 E.5.2.1.3.7 Humidity 507.5/2 E.5.2.1.3.8 Salt Fog 509.5/1 E.5.2.1.3.9 Blowing Dust 510.5/1 E.5.2.1.3.10 Minimum Integrity Vibration 514.6/1 E.5.2.1.3.11 Shock (Functional/Basic) 516.6/1 E.5.2.1.3.12 Shock (Transit Drop) 516.6/4 They shall be equipped with a backlit graphical full-color front-panel display which shall display a minimum of 48 alphanumeric characters, plus a graphical indicator of received signal strength. E.5.2.1.4.1 May 17, 2012 The front-panel display shall be dimmable for nighttime operation. E.5.2.1.5 They shall be equipped with a twelve-button numeric keypad, plus additional buttons as required for the selection of talkgroups, channels and zones. E.5.2.1.6 They shall have a minimum of three configurable (via the programming of the individual Subscriber) buttons on the front panel. The buttons shall be contextsensitive soft-keys. E.5.2.1.7 They shall be equipped with noise suppression circuitry to ensure high intelligibility when transmitting from a high noise environment. E.5.2.1.8 They shall be equipped to transmit their GPS location upon the following events, which shall be configurable via the programming of the individual subscriber: E.5.2.1.8.1 Upon every PTT. E.5.2.1.8.2 Upon activation of the emergency button. E.5.2.1.8.3 Upon receipt of the proper command from the Radio System infrastructure. Document 2 - Specification & Response Document Page 283 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.5.2.1.9 They shall have a low-power mode with a maximum transmit power of no greater than two Watts. The selection of low-power mode shall be slaved to the channel selection mechanism. The high power or low power mode shall be automatically selected upon selection of the desired talkgroup or channel. E.5.2.1.10 They shall be capable of initiation of Individual Alerts and Individual Calls to a specific list of other Subscribers. E.5.2.1.11 E.5.2.1.10.1 The list shall be able to hold at least sixty-four (64) individual PTT ID's. E.5.2.1.10.2 The list shall be independently userprogrammable for each subscriber radio so equipped. They shall be equipped with the Priority Scan feature. E.5.2.1.11.1 E.5.2.2 Type F Mobile The Type F mobile shall have the same features as the Type E Mobile except: E.5.2.2.1 E.5.2.3 May 17, 2012 They shall be available in both remotemount and dash-mount configurations. The Type F Mobile shall be multiband, operating in both the 700 MHz/800 MHz band and the VHF High Band. Type G Mobile The Type G mobile shall have the following characteristics: E.5.2.3.1 They shall be a "middle-tier" product. E.5.2.3.2 They shall be equipped to pass the following MIL-STD810F environmental test procedures: E.5.2.3.2.1 Low Pressure 500.4/1 E.5.2.3.2.2 High Temperature 501.4/1 & 2 E.5.2.3.2.3 Low Temperature 502.4/1 & 2 E.5.2.3.2.4 Temperature Shock 503.4/1 E.5.2.3.2.5 Solar Radiation 505.4/2 E.5.2.3.2.6 Blowing Rain 506.4/1 E.5.2.3.2.7 Humidity 507.4 E.5.2.3.2.8 Salt Fog 509.4/1 Document 2 - Specification & Response Document Page 284 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.5.2.3.3 E.5.2.3.2.9 Blowing Dust 510.4/1 E.5.2.3.2.10 Minimum Integrity Vibration 514.5/1 E.5.2.3.2.11 Shock (Functional/Basic) 516.5/1 E.5.2.3.2.12 Shock (Transit Drop) 516.5/4 They shall be equipped with a backlit front-panel display which shall display a minimum of 36 alphanumeric characters, plus a graphical indicator of signal strength. E.5.2.3.3.1 E.5.2.4 E.5.2.3.4 They shall be equipped with a twelve-button numeric keypad, plus additional buttons as required for the selection of talkgroups, channels and zones. E.5.2.3.5 They shall have a minimum of three configurable (via the programming of the individual Subscriber) buttons on the front panel. The buttons shall be contextsensitive soft-keys. E.5.2.3.6 They shall have a low-power mode with a maximum transmit power of no greater than two Watts. The selection of low-power mode shall be slaved to the channel selection mechanism. The high power or low power mode shall be automatically selected upon selection of the desired talkgroup or channel. E.5.2.3.7 They shall be capable of initiation of Individual Alerts and Individual Calls to a specific list of other Subscribers. E.5.2.3.7.1 The list shall be able to hold at least sixty-four (64) individual PTT ID's. E.5.2.3.7.2 The list shall be independently userprogrammable for each subscriber radio so equipped. E.5.2.3.8 They shall be equipped with the Priority Scan feature. E.5.2.3.9 They shall be available in both remote-mount and dashmount configurations. Type H Mobile The Type H mobile shall have the following characteristics: E.5.2.4.1 May 17, 2012 The front-panel display shall be dimmable for nighttime operation. They shall be a "middle-tier" product. Document 2 - Specification & Response Document Page 285 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.5.2.4.2 E.5.2.4.3 They shall be equipped to pass the following MIL-STD810F environmental test procedures: E.5.2.4.2.1 Low Pressure 500.4/1 E.5.2.4.2.2 High Temperature 501.4/1 & 2 E.5.2.4.2.3 Low Temperature 502.4/1 & 2 E.5.2.4.2.4 Temperature Shock 503.4/1 E.5.2.4.2.5 Solar Radiation 505.4/2 E.5.2.4.2.6 Blowing Rain 506.4/1 E.5.2.4.2.7 Humidity 507.4 E.5.2.4.2.8 Salt Fog 509.4/1 E.5.2.4.2.9 Blowing Dust 510.4/1 E.5.2.4.2.10 Minimum Integrity Vibration 514.5/1 E.5.2.4.2.11 Shock (Functional/Basic) 516.5/1 E.5.2.4.2.12 Shock (Transit Drop) 516.5/4 They shall be equipped with a backlit front-panel display which shall display a minimum of 36 alphanumeric characters, plus a graphical indicator of signal strength. E.5.2.4.3.1 May 17, 2012 The front-panel display shall be dimmable for nighttime operation. E.5.2.4.4 They shall be equipped with buttons as required for the selection of talkgroups, channels and zones. E.5.2.4.5 They shall have a minimum of three configurable (via the programming of the individual Subscriber) buttons on the front panel. The buttons shall be contextsensitive soft-keys. E.5.2.4.6 They shall have a low-power mode with a maximum transmit power of no greater than two Watts. The selection of low-power mode shall be slaved to the channel selection mechanism. The high power or low power mode shall be automatically selected upon selection of the desired talkgroup or channel. E.5.2.4.7 They shall be available in a dash-mount configuration. Document 2 - Specification & Response Document Page 286 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section E.5 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.5 E.5.1 E.5.1.1 E.5.1.1.1 E.5.1.1.2 E.5.1.1.3 E.5.1.1.4 E.5.1.2 E.5.1.3 E.5.1.4 E.5.1.5 E.5.1.5.1 E.5.1.6 E.5.1.6.1 E.5.1.6.2 E.5.1.7 E.5.1.7.1 E.5.1.8 E.5.1.8.1 E.5.1.8.2 E.5.1.9 E.5.1.9.1 E.5.1.9.1.1 E.5.1.9.1.2 E.5.1.9.2 E.5.1.10 E.5.2 E.5.2.1 E.5.2.1.1 E.5.2.1.2 E.5.2.1.3 E.5.2.1.3.1 May 17, 2012 12030-RFP, Document 2, Section E.5 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Document 2 - Specification & Response Document Page 287 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.5.2.1.3.2 E.5.2.1.3.3 E.5.2.1.3.4 E.5.2.1.3.5 E.5.2.1.3.6 E.5.2.1.3.7 E.5.2.1.3.8 E.5.2.1.3.9 E.5.2.1.3.10 E.5.2.1.3.11 E.5.2.1.3.12 E.5.2.1.4 E.5.2.1.4.1 E.5.2.1.5 E.5.2.1.6 E.5.2.1.7 E.5.2.1.8 E.5.2.1.8.1 E.5.2.1.8.2 E.5.2.1.8.3 E.5.2.1.9 E.5.2.1.10 E.5.2.1.10.1 E.5.2.1.10.2 E.5.2.1.11 E.5.2.1.11.1 E.5.2.2 E.5.2.2.1 E.5.2.3 E.5.2.3.1 E.5.2.3.2 E.5.2.3.2.1 E.5.2.3.2.2 May 17, 2012 12030-RFP, Document 2, Section E.5 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Document 2 - Specification & Response Document Page 288 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.5.2.3.2.3 E.5.2.3.2.4 E.5.2.3.2.5 E.5.2.3.2.6 E.5.2.3.2.7 E.5.2.3.2.8 E.5.2.3.2.9 E.5.2.3.2.10 E.5.2.3.2.11 E.5.2.3.2.12 E.5.2.3.3 E.5.2.3.3.1 E.5.2.3.4 E.5.2.3.5 E.5.2.3.6 E.5.2.3.7 E.5.2.3.7.1 E.5.2.3.7.2 E.5.2.3.8 E.5.2.3.9 E.5.2.4 E.5.2.4.1 E.5.2.4.2 E.5.2.4.2.1 E.5.2.4.2.2 E.5.2.4.2.3 E.5.2.4.2.4 E.5.2.4.2.5 E.5.2.4.2.6 E.5.2.4.2.7 E.5.2.4.2.8 E.5.2.4.2.9 E.5.2.4.2.10 May 17, 2012 12030-RFP, Document 2, Section E.5 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. Document 2 - Specification & Response Document Page 289 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.5.2.4.2.11 E.5.2.4.2.12 E.5.2.4.3 E.5.2.4.3.1 E.5.2.4.4 E.5.2.4.5 E.5.2.4.6 E.5.2.4.7 12030-RFP, Document 2, Section E.5 Comply/ Exception Standard/ Custom/ 3rd Party (Choose one) (Choose one) Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. Reason for exception and alternative to specification requirement. {End Section E.5} May 17, 2012 Document 2 - Specification & Response Document Page 290 of 399 Maricopa County, Arizona E.6 12030-RFP P25 Radio System Infrastructure Upgrade Requirements for Control Station Subscriber Radio Equipment Control station radio equipment ("control stations") shall be provided. E.6.1 Requirements Common to All Control Stations E.6.1.1 Control stations shall be permanently installed at fixed locations. E.6.1.2 Control stations shall operate from 120 Volt, single phase AC power. E.6.1.3 The Contractor shall provide and install an antenna, coaxial cable and a lightning suppression device along with each control station. E.6.1.4 Control stations shall be single-band, 700 MHz/800 MHz only. E.6.1.5 Control stations shall have a maximum transmitter RF power output of fifteen Watts. E.6.1.6 Unless a backup power source is already provided by the County, the Contractor shall provide and install an Uninterruptible Power Supply ("UPS") along with each control station. E.6.1.6.1 E.6.2 Types of Control Stations E.6.2.1 Local Control Station Local control stations are meant to be installed in office environments at within easy reach of their operator and shall have the following characteristics: E.6.2.2 May 17, 2012 The UPS shall be equipped to continue powering the associated control station for a minimum of two hours following a loss of primary AC power, with the control station operating on a 5/5/90 duty cycle. E.6.2.1.1 They shall have an attractive outer housing. E.6.2.1.2 They shall be installed complete with a desk microphone and local speaker. E.6.2.1.3 They shall have an on/off control and audio volume adjustment. E.6.2.1.4 They shall be equipped with buttons as required for the selection of talkgroups, channels and zones. E.6.2.1.5 They shall be equipped with a front-panel display which shall display a minimum of 36 alphanumeric characters, plus a graphical indicator of signal strength. Remote Control Station Remote control stations are meant to be installed at locations remote from their operator(s) and shall have the following characteristics: Document 2 - Specification & Response Document Page 291 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade E.6.2.2.1 E.6.2.2.2 E.6.2.2.3 E.6.2.3 May 17, 2012 They shall be equipped with one of the following types of remote control interfaces: E.6.2.2.1.1 A four-wire analog tone remote control using standard EIA format control tones E.6.2.2.1.2 A digital remote control format that provides more features and functions than the analog tone remote control. The remote control interface shall provide the following functions: E.6.2.2.2.1 Transmit E.6.2.2.2.2 Receive E.6.2.2.2.3 Talkgroup or channel select E.6.2.2.2.4 Monitor (tone squelch disable) (conventional only) They shall have a local microphone and speaker. E.6.2.2.3.1 The local speaker shall be muted when not in use. E.6.2.2.3.2 Muting of the local speaker shall not affect receive audio through the remote control interface. Control Stations for Control Channel Monitoring Certain control stations shall be used for off-air monitoring of the control channel data stream. These control stations shall have the following characteristics; E.6.2.3.1 The control station will be programmed to only monitor the current control channel. E.6.2.3.2 If the control channel for the site being monitored changes frequency, the control station will automatically change frequency to match the new control channel. E.6.2.3.3 A microphone and speaker shall not be provided. E.6.2.3.4 The control channel data stream shall be output from the control station in the appropriate format to drive the equipment it is connected to. Document 2 - Specification & Response Document Page 292 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Section E.6 Response Form Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.6 E.6.1 E.6.1.1 E.6.1.2 E.6.1.3 E.6.1.4 E.6.1.5 E.6.1.6 E.6.1.6.1 E.6.2 E.6.2.1 E.6.2.1.1 E.6.2.1.2 E.6.2.1.3 E.6.2.1.4 E.6.2.1.5 E.6.2.2 E.6.2.2.1 E.6.2.2.1.1 E.6.2.2.1.2 E.6.2.2.2 E.6.2.2.2.1 E.6.2.2.2.2 E.6.2.2.2.3 E.6.2.2.2.4 E.6.2.2.3 E.6.2.2.3.1 E.6.2.2.3.2 E.6.2.3 E.6.2.3.1 E.6.2.3.2 E.6.2.3.3 May 17, 2012 12030-RFP, Document 2, Section E.6 Comply/ Exception Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Comply Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Standard Document 2 - Specification & Response Document Page 293 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Respondent’s Statement of Compliance with RFP Specifications Respondent: RFP Section: Requirement Section/ Subsection E.6.2.3.4 12030-RFP, Document 2, Section E.6 Comply/ Exception Standard/ Custom/ 3rd Party 1) Respondent shall indicate compliance or exception to each requirement. If exception, a reason and an alternative must be provided. 2) Respondents shall indicate the feature being provided is a Standard feature, requires Customization, or is being provided by 3rd Party equipment or software. 3) Failure to respond to every requirement may cause the Respondent's proposal to be deemed non-responsive. (Choose one) (Choose one) Reason for exception and alternative to specification requirement. Comply Standard {End Section E.6} May 17, 2012 Document 2 - Specification & Response Document Page 294 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 1 - Defined Areas With Special Coverage Requirements May 17, 2012 Document 2 - Specification & Response Document Page 295 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Greater Phoenix Area (Section D.20.3.3.1) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 296 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Government Center Area (Section D.20.3.3.2) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 297 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Urban Center North Area (Section D.20.3.3.3) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 298 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Queen Creek Area (Section D.20.3.3.4) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 299 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Gila Bend Area (Section D.20.3.3.5) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 300 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Wickenburg Area (Section D.20.3.3.6) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 301 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Fountain Hills Area (Section D.20.3.3.7) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 302 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Cave Creek Area (Section D.20.3.3.8) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 303 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Vekol Valley (Section D.20.3.2.7) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 304 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Paradise Valley (Section D.20.3.2.8) Outlined In Red Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 305 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Lake Pleasant Regional Park (Section D.20.3.2.4.1) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 306 of 399 12030-RFP P25 Radio System Infrastructure Upgrade San Tan Mountain Regional Park (Section D.20.3.2.4.2) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 307 of 399 12030-RFP P25 Radio System Infrastructure Upgrade McDowell Mountain Regional Park (Section D.20.3.2.4.3) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 308 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Usery Mountain Regional Park (Section D.20.3.2.4.4) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 309 of 399 12030-RFP P25 Radio System Infrastructure Upgrade White Tanks Mountain Regional Park (Section D.20.3.2.4.5) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 310 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Apache Lake (Section D.20.3.2.5.5) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 311 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Bartlett Reservoir (Section D.20.3.2.5.2) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 312 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Canyon Lake (Section D.20.3.2.5.4) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 313 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Horseshoe Reservoir (Section D.20.3.2.5.1) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 314 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Saguaro Lake (Section D.20.3.2.5.3) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 315 of 399 12030-RFP P25 Radio System Infrastructure Upgrade Theodore Roosevelt Lake (Section 3.20.3.2.5.6) Outlined In Green Maricopa County, Arizona May 17, 2012 Document 2 - Specification & Response Document Page 316 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 2 - Antenna Sites Currently In Use May 17, 2012 Document 2 - Specification & Response Document Page 317 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Site Name Site Lat Site Lon Site AMSL (ft) Struct Ht (ft) Type Oatman Mountain 33.051139 -113.137806 1724 100 TWR Durango 33.427556 -112.131139 1043 120 TWR Central Courts Building 33.446472 -112.076528 1341 at roof 40 above roof BTWR Southeast Center (Mesa) 33.382111 -111.827750 1210 80 TWR Thompson Peak 33.644222 -111.812083 3953 100 TWR Humboldt Mountain* 33.982806 -111.798472 5151 25 TWR Chandler (911 S. Hamilton)* 33.293080 -111.832374 1220 200 TWR Smith Peak 34.067092 -113.351159 5217 30 TWR White Tanks East 33.567181 -112.558469 3988 100 TWR Yarnell Hill 34.205819 -112.749056 5067 80 TWR Bronco Butte 33.555755 -111.275336 4248 30 TWR Mt. Ord 33.905119 -111.408519 6985 80 TWR Scottsdale Civic Center* 33.490528 -111.920358 1240 110 POLE Mt. Gillen* 33.792028 -112.085611 2127 180 TWR Towers Mountain* 34.23461111 -112.3675556 7616 200 TWR White Tanks West 33.57540556 -112.5789028 4091 40 TWR Emergency Management (County EOC) 33.46954444 -111.9668472 1284 20 TWR Coordinates are NAD83 * Site not owned by Maricopa County May 17, 2012 Document 2 - Specification & Response Document Page 318 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 3 - Diagram of Existing County Microwave Network May 17, 2012 Document 2 - Specification & Response Document Page 319 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Document 2 - Specification & Response Document Page 320 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 4 - List of Shape Files Provided May 17, 2012 Document 2 - Specification & Response Document Page 321 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Defined Area Apache Lake Bartlett Reservoir Canyon Lake Cave Creek Fountain Hills Gila Bend Government Center Greater Phoenix Area Horseshoe Reservoir Lake Pleasant Regional Park May 17, 2012 File Names Included in Zip File apache lake .dbf apache lake.shp apache lake.shx bartlett reservoir.dbf bartlett reservoir.shp bartlett reservoir.shx canyon lake.dbf canyon lake.shp canyon lake.shx cave creek poly.dbf cave creek poly.shp cave creek poly.shx fountain hills.dbf fountain hills.sbn fountain hills.sbx fountain hills.shp fountain hills.shx gila bend.dbf gila bend.sbn gila bend.sbx gila bend.shp gila bend.shx government center.dbf government center.sbn government center.sbx government center.shp government center.shx greater phoenix area.dbf greater phoenix area.sbn greater phoenix area.sbx greater phoenix area.shp greater phoenix area.shx horseshoe reservoir.dbf horseshoe reservoir.shp horseshoe reservoir.shx lake pleasant regional park.dbf lake pleasant regional park.sbn lake pleasant regional park.sbx lake pleasant regional park.shp lake pleasant regional park.shx Document 2 - Specification & Response Document Page 322 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Defined Area McDowell Mountain Regional Park Paradise Valley Queen Creek San Tan Mountain Regional Park Saguaro Lake Theodore Roosevelt Lake Urban Center North Usery Mountain Regional Park Vekol Valley May 17, 2012 File Names Included in Zip File mc dowell mountain regional park.dbf mc dowell mountain regional park.sbn mc dowell mountain regional park.sbx mc dowell mountain regional park.shp mc dowell mountain regional park.shx paradise valley.dbf paradise valley.sbn paradise valley.sbx paradise valley.shp paradise valley.shx queen creek.dbf queen creek.sbn queen creek.sbx queen creek.shp queen creek.shx san tan mountain regional park. dbf san tan mountain regional park. sbn san tan mountain regional park. sbx san tan mountain regional park. shp san tan mountain regional park. shx saquaro lake.dbf saquaro lake.shp saquaro lake.shx theodore roosevelt lake.dbf theodore roosevelt lake.shp theodore roosevelt lake.shx urban center north.dbf urban center north.sbn urban center north.sbx urban center north.shp urban center north.shx usery mountain regional park.dbf usery mountain regional park.sbn usery mountain regional park.sbx usery mountain regional park.shp usery mountain regional park.shx vekol valley.dbf vekol valley.sbn vekol valley.sbx vekol valley.shp vekol valley.shx Document 2 - Specification & Response Document Page 323 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Defined Area White Tank Mountain Regional Park Wickenburg Other Information County-Owned Parcels Inventory of Files in Zip File May 17, 2012 File Names Included in Zip File white tank mountain regional park.dbf white tank mountain regional park.sbn white tank mountain regional park.sbx white tank mountain regional park.shp white tank mountain regional park.shx wickenburg.dbf wickenburg.shp wickenburg.shx File Names Included in Zip File county owned parcels.dbf county owned parcels.sbn county owned parcels.sbx county owned parcels.shp county owned parcels.shx Shape Files List.xslx Document 2 - Specification & Response Document Page 324 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 5 - Standards for Grounding and Lightning and Transient Suppression May 17, 2012 Document 2 - Specification & Response Document Page 325 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade This general specification assumes site sub-surface conditions with average soil resistivity, and the ability to drive ground rods to the specified depth. If these conditions are not met, alternate grounding methods are required, as outlined in section G of this Appendix. A. Conductors - General All conductors are to be run in the shortest, straightest manner possible, with straight vertical or horizontal runs wherever possible. A minimum bending radius of eight inches is required for all conductors. All ground conductors shall be separated by a minimum of 2 inches from signal and control cables, transmission lines, and AC power cables and cords. At points where conductors are routed through holes with sharp edges, the conductor shall be protected with grommets or other material to minimize damage to the conductor or insulation. B. Conductors - Above Ground Except as noted below, #2 AWG or larger solid or stranded non-insulated (bare) copper wire is required. For grounding of equipment and miscellaneous objects, green insulated #2 AWG stranded copper wire with green THHN insulation is required, except where specifically noted. Exterior ground bars shall be connected to the exterior ground ring utilizing two (2) #2 AWG wires separated by a minimum of 12 inches and bonded at opposite ends of the external ground bar. #2 AWG bare tinned solid copper wire is to be used to connect tower guys to the ground rods. C. Conductors - Below Ground Conductors shall be bare tinned solid copper wire #2 AWG, minimum. Ground rods are to be a minimum of 8 ft. in length and 5/8 inches in diameter bare copper or copper clad steel. In areas of corrosive soil, below ground conductors shall be encased in Bentonite or approved equal. D. Connections Between Conductors - Above Ground Exothermic welds must be used for both ends of the following connections: external ground bar to below-ground conductor and tower leg to below-ground conductor. May 17, 2012 Document 2 - Specification & Response Document Page 326 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade For the joining of any other two grounding conductors above ground, either exothermic weld or mechanical connection by split-bolt (copper alloy or pressure type crimp connectors) are acceptable, except crimp connections are not to be used on solid wire. Mechanical ground connections to galvanized steel are to be done with tinned copper wire and bronze, stainless steel, bi-metallic transition, or galvanized steel clamps or split-bolts. Where connections are made between conductors, the point of attachment shall always point in the direction of current flow toward earth ground. Connections Between Conductors - Below Ground All below ground connections shall be exothermically welded. Connections to Equipment and Equipment Mounting Structures Connection of ground conductors to equipment shall be by the use of lugs or clamps appropriate to the size and type of wire and equipment being grounded. E. Surface Preparation Prior to Connection Whether connection is to be mechanical or exothermic weld, the surfaces of each conductor to be connected are to be well cleaned, removing all paint, coatings, oil, dirt, and corrosion before each joint is made. An appropriate type of listed, conductive anti-oxidant shall be applied on all connections of dissimilar metals. Copper enhanced anti-oxidant compound should be used between copper, brass, bronze and tin-plated bonding surfaces. Zinc enhanced anti-oxidant compound should be used between tin-plated connection devices and steel, galvanized steel, zinc-chromate steel, aluminum, and tin-plated copper bus bar bonding surfaces. Where threaded or tapped holes are provided for attachment purposes, a star or split type lock washer shall be installed under the head of the screw or bolt and/ or between the nut and the ground bus bar. Self-tapping or sheet metal type screws shall not be used for attaching ground or grounding conductors to any surface. Mating surfaces are to be clean and flat. Two-holed lugs are required on all ground leads attached to the external or internal ground bars, and are preferred in any situation where strain on the wire might exert sufficient stress to loosen a single mounting bolt. May 17, 2012 Document 2 - Specification & Response Document Page 327 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Stainless steel mounting hardware is required on all outside connections as well as on the internal ground bar, and is preferred on all ground connections. Lugs may be tinned rather than stainless steel. Hardware and lug bolt sizes are to be properly matched for minimal play in mechanical assembly. Split ring type lock-washers are to be used to prevent nuts from loosening. "Daisy-chaining" of ground conductors between multiple pieces of equipment and the main or subsidiary ground conductor shall not be permitted. Precautions against the use of connections between dissimilar metals must be observed. The following tables summarize the requirements: Group I Magnesium Aluminum Zinc F. Group II Tin Lead Steel Group III Stainless Steel Nickel Iron Group IV Copper Silver Contact Surfaces Within same group Adjacent groups Inside OK Outside OK OK Separated one group Separated two groups OK Waterproof coating must be applied after direct metal-to-metal contact. No water allowed to bridge gap. Same as above OK Appropriate passivation of contact surfaces or use of special transition clamps or transition materials between mating surfaces. Practices to be Avoided Ground conductors shall not be run through metal conduit, unless wire is permanently bonded at both ends of the conduit. The use of PVC conduit is preferred. The ground wire (green or bare wire) of AC power circuits shall not be used for lightning ground. Bare copper conductors shall be installed so that they do not contact any aluminum or galvanized steel surfaces. Where contact is unavoidable, conductors shall be insulated, enclosed in PVC conduit, or placed on standoffs to prevent contact. No holes shall be drilled into towers, nor shall tower bolts be loosened for the attachment of grounds. May 17, 2012 Document 2 - Specification & Response Document Page 328 of 399 Maricopa County, Arizona G. 12030-RFP P25 Radio System Infrastructure Upgrade External Ground System Soil resistivity at each Site shall be measured using the 4-point Wenner method using a properly calibrated ground resistance measurement device. The results shall be used to produce an external ground system design for each Site. Adverse soil conditions, such as shallow or no topsoil, or poor soil conductivity may prevent the use of buried ground rods and/or buried conductors. In those cases, at least one of the following shall be used: 1. Chemical ground rods 2. Chemical ground rods designed for shallow burial 3. Extension of ground conductors to a location where better soil is found 4. A grid or radial ground system. The external ground system shall consist of the Equipment Shelter External Ground Ring and the Tower Ground Ring. The two ground rings shall be connected using buried #2 AWG bare tinned solid copper wire exothermically welded at each end, buried at the same depth as the ground rings. The External Ground System shall have a resistance to earth ground of not more than 10 Ohms. Five Ohms or less is desired, if possible. The resistance to ground of the external ground system shall be measured prior to connection to the Internal Ground System or to the electrical power ground. Measurements shall be made using the 3-stake "fall of potential" method using a properly calibrated ground resistance measurement device. H. Equipment Shelter External Ground Ring Ground rods shall be placed at each corner of the shelter, in a line approximately 36 inches from and parallel to the perimeter of the building, and additional rods shall be added to reduce the maximum spacing between ground rods to between 16 and 25 feet. Ideally, ground rods should be spaced at 2 times their length. A ground rod shall be placed directly below the transmission line entry port and directly below the AC service entrance. The tops of the ground rods are to be driven to a minimum depth of 30 inches below finished grade or 6 inches below frost line. The proper tool shall be used to drive the ground rods to prevent rod deformation. Ground rods shall be interconnected using a ring of #2 AWG bare solid copper wire exothermically welded to the top of the ground rods and placed at the same depth as the top of the ground rods. May 17, 2012 Document 2 - Specification & Response Document Page 329 of 399 Maricopa County, Arizona I. 12030-RFP P25 Radio System Infrastructure Upgrade Tower Ground Ring - Self-supporting Lattice Towers Ground rods shall be placed at each tower leg, approximately 36 inches out from the tower leg foundation, and additional rods shall be added to reduce the maximum spacing between ground rods to between 16 and 25 feet. Ideally, ground rods should be spaced at 2 times their length. The tops of the ground rods shall be driven to a minimum depth of 30 inches below finished grade or 6 inches below frost line. The proper tool shall be used to drive the ground rods to prevent rod deformation. Ground rods shall be interconnected using a ring of #2 AWG bare tinned solid copper wire exothermically welded to the top of the ground rods and placed at the same depth as the top of the ground rods. Ground rods are to be attached to the tower legs with a #2 AWG bare tinned solid copper wire exothermically welded to top of ground rods and to the tower legs. Spray galvanizing compound shall be used to repair any galvanizing that is damaged by the exothermic weld. J. Tower Ground Ring - Guyed Lattice Towers or Monopoles Three ground rods are to be placed in a ring approximately 36 inches out from the tower foundation. Ground rods are to be evenly spaced around the base of the tower. The tops of the ground rods shall be driven to a minimum depth of 30 inches below finished grade or 6 inches below frost line. The proper tool shall be used to drive the ground rods to prevent rod deformation. Ground rods shall be interconnected using a ring of #2 AWG bare tinned solid copper wire exothermically welded to the top of the ground rods and placed at the same depth as the top of the ground rods. The ground ring shall be attached to the base of the tower in two (2) locations with #2 AWG bare tinned solid copper wire exothermically welded to the ground ring and to the tower base. Spray galvanizing compound shall be used to repair any galvanizing that is damaged by the exothermic weld. For guyed towers, each guy wire shall be grounded at the anchor point by one (1) ground rod below the anchor approximately 1 foot from the anchor foundation and driven to a minimum depth of 30 inches below finished grade or 6 inches below frost line. The ground rod shall be connected to each guy wire in accordance with Sections C and D of this Appendix. K. Ground Test Well May 17, 2012 Document 2 - Specification & Response Document Page 330 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade A ground test well is to be provided at one point along the external ground system for measuring ground resistance. The test well shall consist of a 6 inch diameter by 24 inch deep schedule 80 PVC inspection well placed over a ground rod. The pipe shall have a screw type cover to keep dirt and debris from entering the test well. The PVC pipe shall extend approximately 1 inch above finished grade. The lid and pipe extension shall not exceed 2 inches above finished grade. The ground rod shall be driven to a depth of approximately 6 inches below finished grade. The rod shall extend approximately 18 inches above the bottom of the PVC pipe with 6 inches of gravel fill added. A Burndy #GAR6426 or equivalent connection to the test well ground rod will be made approximately 1 inch below the top of the rod. This connection point will differ from the buried depth of the ground ring. L. Transmission Line Grounding All transmission line and waveguide outer conductors are to be grounded at the following locations: 1. At the bottom of the vertical run on the tower 2. At vertical intervals of no more than 150 feet from the base of the tower 3. At the top of the vertical run on the tower 4. At the cable entry port of the equipment shelter Transmission lines and waveguides shall be grounded by cable manufacturer's recommended grounding kit for the type of transmission line used. All ground kits shall be attached in a manner that permits the connecting wire to be routed vertically. Each coaxial transmission line shall have installed a coaxial surge suppression device, Polyphaser model IS-B50HN-C0 or approved equal. The surge suppression device shall be mounted inside the equipment shelter of equipment room, as close as possible to the cable entry port. The device shall be grounded to the equipment shelter interior main ground bar, using no less than #6 AWG bare or insulated stranded copper wire. The ground wire shall be run in the shortest, straightest manner possible. M. External Ground Bar The external ground bar shall be tinned copper, pre-drilled and sized to accommodate all ground connections without the need to mount multiple lugs on one hole. It shall be mounted below the cable entry port panel and shall be connected to the external ground ring in accordance with Sections C and D of this Appendix. Copper ground bars shall be permanently stamped or engraved with the letters "MC" on the back side (the side normally not readily visible) of the bar for identification purposes in the event of copper theft. N. Cable Entry Port May 17, 2012 Document 2 - Specification & Response Document Page 331 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade The cable entry port panel is to be connected to the external ground bar with bare #2 AWG stranded or solid copper wire mechanically bonded at both ends in accordance with Sections C and D of this Appendix. O. Fences Metallic fences are to be grounded if the distance between the fence and any ground ring or grounded object is 20 ft. or less. All corner posts and every other fence post shall be connected to the nearest point of an external ground ring with #2 AWG bare solid copper wire, buried at the same depth as the ground ring. Exothermic welds are to be used for all connections. Spray galvanizing compound shall be used to repair any galvanizing that is damaged by the exothermic weld. The gate(s) are to be connected to the supporting fence posts utilizing either a flexible tinned copper ground strap or flexible insulated #2 AWG stranded copper wire at the top and bottom of the gate. P. Electrical Service Entrance The electrical service entrance ground is to be connected to the exterior equipment shelter ground ring in accordance with Sections C and D of this Appendix. Q. Air Conditioning Units Air conditioning units are to be grounded to the external ground ring using #2 AWG solid bare copper wire exothermically welded at the ground ring and mechanically bonded at the air conditioning units. R. Cable Bridge/Ice Shield Cable bridges/ice bridges are to be grounded to the external ground ring at all support posts using #2 AWG solid bare copper wire, exothermically welded at both ends. Spray galvanizing compound shall be used to repair any galvanizing that is damaged by the exothermic weld. If no support poles are used, the cable bridge/ice bridge is to be connected to the external ground bar using #2 AWG stranded bare copper wire mechanically attached at both ends. S. Emergency Generator If the emergency generator is mounted external to the building, the generator and any supporting platform or base are to be grounded to the external ground ring using #2 AWG solid bare copper wire exothermically welded at the ground ring and mechanically bonded at the generator. May 17, 2012 Document 2 - Specification & Response Document Page 332 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade An exterior-mounted manual transfer switch is to be grounded to the external ground ring using #2 AWG solid bare copper wire exothermically welded at the ground ring and mechanically bonded at the manual transfer switch. T. Fuel Tank(s) Fuel storage tank(s) shall be grounded to the external ground ring using #2 AWG solid bare copper wire exothermically welded at the ground ring and mechanically bonded at the tank(s). U. Additional Exterior Metal Objects Any metal objects within 20 ft. of any grounded object or ground ring are to be grounded to the external ground ring using #2 AWG stranded or solid bare copper wire exothermically welded at the ground ring and exothermically or mechanically bonded at the metal object. This is to include any metal building parts not otherwise grounded by the internal ground ring. V. Interior Single Point Ground System The master ground bar (MGB) will serve as the central ground node of the internal grounding system. The MGB shall be mounted on insulators in a central location (typically just below the transmission line cable entry port). The MGB shall be connected to the external ground system using a single #2 AWG solid bare copper wire exothermically welded to the external ground system and exothermically welded or mechanically attached to the MGB. The conductor shall be routed through the wall using a PVC conduit that shall be sealed at both ends following insertion of the conductor. Subsidiary ground conductors shall extended throughout the room from the master ground bar. Connection in a loop or ring is prohibited. Sub-system ground bars (SSGB) shall be used where appropriate. Subsidiary ground conductors shall consist of #2 AWG stranded copper wire, routed along the inside perimeter walls of the shelter approximately 6 inches below the ceiling and mechanically bonded to the MGB. Insulated mounting standoffs shall be installed every 2 ft. or as required to accommodate bends. If the building includes an attached generator room, a subsidiary ground conductor shall be extended into the generator room through a PVC sleeve or conduit, and shall be mechanically bonded to a generator room SSGB. Additional subsidiary ground conductors shall be run from the SSGB to the points to be grounded. Copper ground bars shall be permanently stamped or engraved with the letters "MC" on the back side (the side normally not readily visible) of the bar for identification purposes in the event of copper theft. W. Telephone and Control Circuits May 17, 2012 Document 2 - Specification & Response Document Page 333 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade All telephone circuits and control circuits entering a equipment shelter or equipment room shall be protected with lightning surge suppressors of the appropriate type and rating. These protectors will be located as close as possible to the point that the circuit(s) enter the building, and shall be connected to the interior ground system using #6 AWG green insulated stranded copper wire, in accordance with Sections C and D of this Appendix. X. Main AC Electrical Distribution Panel Protection The main AC electrical distribution panel is to be protected by a Type I suppression device. Type I suppression devices provide a minimum of 250 joules of Silicon Avalanche Diodes (SAD) as primary protection and a minimum of 5000 joules of Metal Oxide Varistors (MOV) as secondary protection. The surge suppression device shall provide separate dry contact closures to indicate the activation of suppression circuits and to indicate suppressor failure. Y. Equipment and Racks Each individual piece of equipment and rack shall be individually connected to the interior ground system using no less than #6 AWG green insulated stranded copper wire, mechanically bonded on both ends. "Daisy-chaining" of ground conductors between multiple pieces of equipment and the main or subsidiary ground conductor shall not be permitted. If it is necessary to minimize the number of individual ground conductors, a ground bus may be used. Each rack shall have a separate ground bus consisting of a #2 AWG bare stranded copper wire. Each bus shall be connected to the MGB. Individual equipment ground conductors may be connected to the ground bus. Z. Transmission Line Entry Port The transmission line entry port shall be mechanically bonded to the MGB using green insulated #2 stranded copper wire. AA. Electrical Equipment Electrical distribution panel(s), UPS equipment, generator transfer switch, fire suppression system, tower light controller, rectifiers and chargers, battery racks, electrical conduit, and cable ladders shall be connected to the interior ground system using no smaller than #6 AWG green insulated stranded copper wire. Cable ladder mechanical junctions shall be jumpered and mechanically bonded using #6 AWG green insulated stranded copper wire. BB. HVAC Systems The air conditioner controller panel and all vents, louvers ducts and fans shall be mechanically bonded to the interior ground system using no smaller than #6 AWG green insulated stranded copper wire: CC. Doors and Doorframes May 17, 2012 Document 2 - Specification & Response Document Page 334 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade All metal doorframes shall be mechanically bonded to the interior ground system using no smaller than #6 AWG green insulated stranded copper wire. Metal doors shall be mechanically bonded to doorframes using flexible #2 AWG insulated stranded copper wire. DD. Grounding in Existing Buildings The grounding requirements in a building shall be the same as in a communications equipment shelter, except that connection to an exterior ground ring may not be possible. The following methods shall be used as a source for obtaining, routing, and connecting earth ground: 1. A metal water pipe that runs at least 10 feet in direct contact with the earth and provided that there is low-resistance electrical continuity between the grounding point and the earth. CAUTION: DO NOT USE A GAS PIPE AS THE GROUNDING ELECTRODE 2. The metal steel frame of the building itself where it is effectively grounded. In case there is doubt in the integrity of the most desirable grounding point in a building, the building ground resistance shall be measured and verified that it does not exceed 10 Ohms. - End of Appendix 5 - May 17, 2012 Document 2 - Specification & Response Document Page 335 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 6 - Requirements and Procedures for Radio Coverage Verification Acceptance Testing May 17, 2012 Document 2 - Specification & Response Document Page 336 of 399 Maricopa County, Arizona A. 1. 2. B. 1. 2. 3. 12030-RFP P25 Radio System Infrastructure Upgrade GENERAL INFORMATION The definitions of the various levels of DAQ shall be the Subjective Performance Descriptions of each level contained in TIA/EIA Telecommunications Systems Bulletin TSB88-B, "Wireless Communications Systems - Performance In Noise and Interference-Limited Situations Recommended Methods For Technology-Independent Modeling, Simulation, and Verification," latest revision (“TSB-88”). In addition to the test procedures described below, the Contractor shall record trunked control channel signal strength levels (from repeater transmitter only) continuously during the testing. The geographic location (in degrees, minutes, seconds and tenths of seconds of latitude and longitude, NAD83 datum) of each test point shall also be recorded. This information shall be recorded using an integrated computerized GPS location and signal measurement system. VOICE TEST PROCEDURES Since DAQ is, in part, evaluated on the need to repeat transmissions, the voice tests shall be performed using a pre-prepared list of short, random phrases. This is to prevent test participants from knowing or guessing the content of a transmission in advance and consequently scoring the transmission higher than it deserves because repetition was not required. The list shall be prepared ahead of time but not revealed to either the Field Testers or the Dispatch Testers until the time of the test. The Field Testers shall not be given the list of phrases at any time. The list shall contain enough phrases so that each phrase will be repeated no more than once during the course of the test. Areas To Be Tested. a. Voice Radio Coverage Verification Testing shall be conducted within the areas identified on the Contractor’s Coverage Map(s) as meeting the criteria for Portable Coverage as defined in Section D.20 of the Technical Specifications. b. The area to be tested shall be laid out on a suitable map of the County showing streets, major County buildings and major landmarks. The area shall be divided into a grid of squares. In urban and suburban areas, grid squares shall be one-quarter mile to a side. In rural areas (except for Saguaro Lake, Canyon Lake, Apache Lake, Bartlett Reservoir, and Roosevelt Lake), grid squares shall be one mile to a side. For Saguaro Lake, Canyon Lake, Apache Lake, Bartlett Reservoir, and Roosevelt Lake, the grid squares ahell be onequarter mile to a side. Each grid square shall be assigned a unique identifier. c. Grid squares that are inaccessible to Field Testers shall be marked as such and shall be excluded from the test. Field-To-Dispatch Test. A minimum of two individuals shall be designated as a Field Test Team. One of the two shall be a representative of the County, the other shall be a representative of the Contractor. Field testers shall make and receive radio transmissions in the field and document the received audio quality. There shall be a sufficient number of Field Test Teams to complete all Radio Coverage Verification Acceptance Testing within the required schedule timeframe. Field testers shall travel to a randomly-selected point within one of the grid squares and do the following: a. On a pre-prepared test results form, record the identifier of the grid square in which they are located and another description of their location (example: “3324 West Gibson Lane, Phoenix”). May 17, 2012 Document 2 - Specification & Response Document Page 337 of 399 Maricopa County, Arizona b. c. d. e. 12030-RFP P25 Radio System Infrastructure Upgrade Using a portable radio, report the identifier of the grid square and other description of their location to the Dispatch Tester. Do not repeat any information and do not say anything additional. Using the portable radio, listen for the Dispatch Tester to read back the grid identifier and the location description. Verify that it is correct. Listen for the Dispatch Tester to read a short, random phrase. Upon receiving the test phrase they shall evaluate its audio quality and record the DAQ level (from 1 to 5) in the test results form. Transmit the exact phrase back to the Dispatch Tester for verification that it is correct. Inform the Dispatch Tester that the test for that grid square is completed. Move to another grid square and repeat a. through e., above. 4. Dispatch-To-Field Test. One or more County dispatchers shall be designated as Dispatch Testers. Dispatch Testers shall make and receive radio transmissions at the County's Dispatch Center and document the received audio quality. A representative of the Contractor shall also be present in the Dispatch Center during testing. Dispatch testers shall be stationed at a radio control console in the County Dispatch Center and shall do the following: a. Listen for the field testers to report their current grid square and location description. On a pre-prepared electronic test results form, record the Field Tester's grid square and location. Evaluate the quality of the audio and record the DAQ level (from 1 to 5) in the test-results form. b. Over the radio, read back the Field Tester's grid identifier and location description, and then immediately read a short, random phrase from the list provided. c. Listen for the Field Tester to transmit the phrase back, and verify it is correct. d. Listen for the Field Tester to report that the test for that grid square is completed and acknowledge. C. AREAS WHERE ADDITIONAL SIGNAL STRENGTH MARGINS ARE REQUIRED FOR BUILDING PENETRATION The Contractor shall provide signal strength measuring and recording devices to measure actual signal strength levels for both the talk-out and talk-back directions. Measurements shall be made at least once in each direction per grid square that is not excluded as provided in Paragraph B.2.c., above. Measurements shall be made outdoors and the measuring and recording equipment shall be calibrated to simulate a portable radio worn on-hip. D. 1. CRITERIA FOR SUCCESS Contractor's Coverage Map shall be overlaid onto the grid map. Grid squares that are not expected to have DAQ 3.4 or better shall be tested (for informational purposes only) but shall be excluded from the determination of success or failure. Voice Radio Coverage Verification Testing shall be deemed successful if: a. 95% or more of all grid squares not excluded (as provided in Paragraph B.2.c., above) achieve a DAQ of 3.4 or better, and b. 95% or more of all signal strength measurements made pursuant to C., above, equal or exceed the predicted signal strength level in both directions (talk-out and talk-back). 2. E. TEST RESULTS Test results shall be provided to the County in the form of a written summary and maps of the test area overlaid with the grid squares tested and the DAQ rating for each grid square. Separate May 17, 2012 Document 2 - Specification & Response Document Page 338 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade maps shall be prepared and submitted for the Dispatch-to-Field test and the Field-to-Dispatch test. The Contractor shall provide an additional map containing a graphic representation of the signal strength measured in each field location. The Contractor shall provide the County with copies (on CD-ROM or DVD-ROM) of all computer files containing the raw signal strength vs. location data. - End of Appendix 6 - May 17, 2012 Document 2 - Specification & Response Document Page 339 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 7 - Requirements and Procedures for Ninety-Day Reliability Testing May 17, 2012 Document 2 - Specification & Response Document Page 340 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade The Radio System shall be commissioned and placed into normal operation. Upon commissioning, the system shall undergo a Sixty-Day Reliability Test. The test shall be considered to be completed successfully after a period of sixty (60) calendar days in normal operation in which no communication outages or degradation to communications quality occur that are attributable to the work performed or the materials provided by the Contractor. The test shall start at 8:00 AM on the next calendar day following successful commissioning of the Radio System. Communication outages or degradation to communications quality that are not attributable to the work performed or the materials provided by the Contractor shall not be charged against this Sixty-Day Reliability Test. Should such failures occur, the test shall be suspended until such time as the problem is corrected. The test shall then be re-started from the time it was suspended. The duration of the test suspension shall not count as part of the 60 day test. Should communication outages or degradation to communications quality occur for reasons that are attributable to the work performed or the materials provided by the Contractor, the faulty work or defective materials shall be repaired or replaced at no cost to the County and the test shall then be re-started from the first day. The Contractor shall document all communications outages or degradation to communications quality whether or not they are attributable to work or materials provided by the Contractor. Test start and stop dates and times, explanations for the outages or degradation and all corrective action shall be included in the documentation. A copy of the document shall be provided to the County weekly during the test, and the completed original document shall be provided to the County upon successful completion of the test. - End of Appendix 7 - May 17, 2012 Document 2 - Specification & Response Document Page 341 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 8 - Construction Requirements for Buildings Built On-Site May 17, 2012 Document 2 - Specification & Response Document Page 342 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Document 2 - Specification & Response Document Page 343 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Document 2 - Specification & Response Document Page 344 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Document 2 - Specification & Response Document Page 345 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 9 - Cabling Specification for Data Center Environments May 17, 2012 Document 2 - Specification & Response Document Page 346 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Maricopa County Standard Number: A1201-S-02 Structured Cabling Standards Category: Information Technology – Telecommunications Revision: 4 Issued: November, 2011 Initiated by: Office of Enterprise Technology Revised: Al Brown, RCDD Reviewed by: OET A. Purpose The purpose of this document is to establish consistent, County-wide communications wiring installation standards for network cabling within Maricopa County facilities undergoing new construction and/or major renovations. NOTE: The words "should" and "must" shall be construed to mean "shall." B. Reference This document is based upon BICSI standards and references from the 2006 Telecommunications Distribution Methods Manual (Twelfth Edition, Volumes One & Two), along with applicable state and local codes and standards. MC-OET reserves the right to require more stringent standards where applicable. C. Standard All communications wiring plans for new construction and major renovations must comply with the requirements outlined in this document. In general, the Contractor shall be responsible for the installation, termination, testing and documentation of all specified communications cable. All existing installations in the downtown campus use a Panduit solution with Category 6 cabling. Remote locations may use a Leviton solution with Category 6 cabling, unless a Panduit solution is already present. Verify product requirements specific to each site with the Maricopa County OET Program Manager, Infrastructure Project Manager, IT Senior Manager or MC-OET point of contact prior to placing any material orders. Sumitomo tube cell and Air-blown fiber (ABF) is used to interconnect multiple closets within the same building and between floors. Manholes and vaults throughout the Maricopa County campuses will be connected with the appropriate type of tube cell and ABF. At the completion of all projects, MC-OET reserves the right to require the Contractor to perform random tests witnessed by the Maricopa County Telecommunication Project Manager. Additional testing may be required if random testing determines that factory specifications have not been met. See Section 4: Testing, for specific test requirements and procedures. At the completion of a work order or project, the Contractor shall provide the following documentation to MC-OET as specified in detail in Section 5, Deliverables:  All as-built drawings will be done in CAD and shall be provided to MC-OET in an electronic format. Hard copies must be available upon request.  As-built drawings must identify voice and data drops along with any cable pathways.  Electronic copies of the test results for all copper and fiber installed. May 17, 2012 Document 2 - Specification & Response Document Page 347 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade  Copy of the warranty punch list developed by the contractor and the manufacturer during their initial walk-through. The document is divided into six sections: Section 1 – General Requirements Section 2 - Horizontal Cabling Section 3 - Vertical Cabling Section 4 - Testing Section 5 - Deliverables Section 6 - Parts List Section 1 describes standard cabling procedures which apply to any network cabling installation. Sections 2 and 3 are specific to the installation procedures and type of network being installed. Sections 4 and 5 relate to testing and final deliverables. Section 6 lists the most common components used for the network installations. SECTION 1: General Requirements A. A scope of work and work order number is required prior to authorization to proceed on any work. A Bill of Materials (BOM) must be submitted for all work orders larger than 10 drops. All other work orders performed shall contain a list of materials used. The list shall contain the vendor name (i.e. Panduit, Leviton, etc), a part number or description, and number or length of each item used (refer to Section 6, Parts List). Contractors will maintain work site cleanliness at all times. All trash and garbage must be removed from the worksite daily. Beverage and food containers are not allowed in any of MC-OET Data Centers and or Equipment Rooms (ER)/Telecommunications Rooms (TR). Materials purchased for the project or work order will only be unpackaged as needed. Materials left after the completion of a project or work order must be returned to inventory. All items being returned must contain all parts – screws, labels, etc. (Parts must not be taken out of another box if a box has been opened and items are missing.) Dirt and dust contamination can degrade fiber optic cable performance significantly. Fiber optic couplers and fiber optic patch cables shall be protected at all times prior to installation of the fiber optic patch cables by installing dust caps. Retain dust caps that are removed during the installation of the fiber patch cables, store in a suitable container, and place the container in the fiber termination enclosure. Immediately replace dust caps on patch cables and couplers after any field changes to the network are completed. Any fiber jumper not in-use shall be removed from the cable management, capped and returned to the inventory. Removal of ceiling tile, drilling into cement walls, wood, or other materials within the room results in fine dust released into the air. Appropriate precautions are required to keep this dust from falling on or around any networking equipment installed in a telecommunications room. These precautions must be taken regardless of whether or not the equipment is activated. If the equipment is activated (operational), then additional care must be taken to ensure that air-flow is not restricted. May 17, 2012 Document 2 - Specification & Response Document Page 348 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade All changes made to the infrastructure shall be properly labeled and documented according to TIA/EIA 606-A Labeling Standard and County requirements. MC-OET requirements are provided in more detail under Section 5 – Deliverables. All patch cords and fiber jumpers shall be 100% tested and certified by the manufacturer to meet or exceed the Category 6 copper and 10 Gigabit fiber standards. MC-OET may request supporting documentation published by the manufacturer. Channel testing shall not be permitted to ensure that copper patch cords and fiber jumpers independently meet the required performance standards of Category 6 copper or 10 Gigabit fiber. As part of the project scope of work, MC-OET may require a percentage of horizontal cables to be channel tested after the installation process is complete. The Leviton/Fluke JackRapid™ tool shall be used for all Leviton Quick Port CAT6 outlet module terminations. Use of any other tool to complete the termination process is prohibited. Panduit Mini-Com® CAT6 outlet modules shall be terminated using the Panduit TGJT Termination Tool. Use of any other tool to complete the termination process is prohibited. All work area locations will have three cable runs. Two (2) category 6 cables runs will be terminated for data. One (1) Category 3 cable run will be split and terminated to two (2) Category 3 USOC jacks for voice (refer to the horizontal cabling details in Section 2, Horizontal Cabling, before construction is started). All coaxial cable will be installed as described in the project requirements of the scope of work (SOW). See Section 4: Testing, for specific test requirements and procedures for testing. The installation and test results will be verified by MC-OET Project Manager and/or Lead Technician. CATV Applications- RG6, 18 AWG, quad shield, 75 ohm nominal impedance, copper clad steel center conductor with foam dialectric, 100% aluminum/polyester tape with a minimum of 60% aluminum braid shield. For CATV applications the maximum cable run length for RG6 cable should not exceed 150’. When installing coaxial cable do not exceed the minimum bend radius requirements or the maximum pulling tension as specified by the cable manufacturer or permanent damage to the cable may occur. Cable damaged during the installation process shall be replaced at the contractor’s expense. F-type compression connectors shall be utilized for coaxial cable terminations. At the completion of a project consisting of 30 or more drops, the contractor shall schedule a final walk-through with MC-OET Project Manager and/or Lead Technician. The cabling contractor will provide MC-OET with a timeline and plan for addressing any punch list or warranty items. In addition, a meeting shall be scheduled with the cabling vendor to conduct a walk-through to complete the warranty requirements. TELECOMMUNICATIONS SPACES: Telecommunications spaces are defined as: Telecommunications Room (TR) Equipment Room (ER) May 17, 2012 Document 2 - Specification & Response Document Page 349 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Entrance Facility (EF) Considerations common to TRs, ERs, and EFs are shown in this section. Telecommunications spaces shall be a rectangular room with minimum floor dimensions of 10 ft x 8 ft. There shall be at least one ER or TR per floor. (TDMM, p. 6-23) When the number of work areas to be served is known, the Telecommunications room floor space should be equal to 0.75 square feet of space multiplied by the number of work areas. If the number of work areas is unknown, calculate the square footage of floor space required by dividing the amount of usable floor space by 100 ft2 per 110 square feet of work area space served (TIA/EIA-569-A). All Floors will have VCT Tile (Non-Static Preferred). Carpet as a floor covering is prohibited. Bare concrete is easily chipped creating dust particles which can cause damage to network equipment. Other treatments, paints or coatings for floors can be used if specifications indicate dust and static electricity are minimized with the particular type chosen. Floor coverings for telecommunications spaces must be approved by the Maricopa County OET Project Manager during the design phase of the project. Install 4’x 8’x ¾” fire retardant A/C grade or better, void-free plywood per TIA/EIA-569-A standards on 3 walls. The grade A side is the side exposed. (TDMM, page 6-19) If approved by MC-OET, the plywood may be treated with at least two coats of fire retardant paint on all sides per TIA/EIA 569A standards instead of using fire retardant plywood. Allow a minimum of 3.28 ft. wide x 3.28 ft. deep and 7.5 ft. high for equipment racks, cabinets and enclosures. Allow a minimum of 3.28 ft. of aisle space in-front of and to the rear of the space allocated for the equipment racks, cabinets or enclosures. (TDMM, p. 647) One or more load bearing walls should be incorporated into the design of all Telecommunications Spaces. This reduces the possibility of relocating the telecommunications space if the floor or building is expanded or altered in the future. (TDMM, p. 6-13) Sleeves, slots and conduits should be located on the left side of the room to enhance left to right expansion. Telecommunications spaces shall be dedicated for telecommunications use. Do not locate building custodial services (sinks, cleaning materials, mops, electrical system transformers, sources of EMI, etc.) in Telecommunications spaces. ENVIRONMENTAL CONTROL FOR ER’S AND TR’S Maintain room temperature between 64 degrees and 75 degrees (F) with relative humidity range from 30 % to 55% (non-condensing). This should be maintained constantly 24 hours by 7 days a week. BTU requirements will be established based on equipment to be installed. If no active equipment is located in the room, temperature may vary from 50 - 95F. (TDMM, pages 6-10 and 6-55) May 17, 2012 Document 2 - Specification & Response Document Page 350 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade ELECTRICAL POWER FOR ER’S AND TR’S New Construction Projects or existing County buildings involved in the infrastructure upgrade will require electrical power to support the equipment being installed, and to ensure redundancy. The following sections list the minimum power requirements for ERs and TRs. Additional electrical power requirements may be applicable depending on but not limited to factors such as on the size and shape of the ER/TR and additional equipment requirements. Verify all power requirements including but not limited to the location of the outlets and quantity of circuits required with the OET project manager prior to installation. Convenience Outlets. At least two (2) duplex non-switched 120VAC electrical outlets (NEMA 5-20R) located on opposite walls for tools and test equipment and placed on a separate circuit from those serving the Telecommunications equipment are required for each ER/TR. (TDMM, page 7-10). Catalyst 6500 series and 4500 series equipment power requirements Each Catalyst 6500 series and Catalyst 4500 series chassis is installed with two (2) power supplies. Two (2) 20A, 250VAC, separate and dedicated branch circuits with NEMA 6-20R grounded receptacles and protected by separate two-pole circuit breakers are required for each chassis. Allow for a minimum of four (4) 6500/4500 series chassis to be placed in each TR/ER. The source AC outlets must be within 6’ of the system and easily accessible. Outlets shall be located on the outside of the cable support tray unless otherwise noted. AC-input power supplies require single-phase source AC. All AC power supply inputs shall be fully isolated. UPS models utilizing ferroresonant technology shall not be utilized with the 6500 series chassis. Some uninterruptible power supply (UPS) models that use ferroresonant technology can become unstable when operating with the Catalyst 6500 series switch power supplies which use power factor correction (PFC). This can cause the output voltage waveform to the switch to become distorted resulting in an undervoltage situation in the system. Catalyst 3750 series equipment power requirements Each Catalyst 3750 is installed with two (2) power supplies. Two (2) 20A, 125VAC separate and dedicated branch circuits with NEMA 5-20R power receptacles are required for each power supply. Allow for a minimum of two (2) 3750 series chassis to be placed in each TR/ER. The source AC outlets must be within 6’ of the system and easily accessible. Outlets shall be located on the outside of the cable support tray unless otherwise noted. May 17, 2012 Document 2 - Specification & Response Document Page 351 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade AC-input power supplies require single-phase source AC. All AC power supply inputs shall be fully isolated. CONDUIT REQUIREMENTS FOR ER’S AND TR’S Maricopa County requires a minimum of two 4” conduits from the Entrance Facility (EF) to the property line for QWEST, and two 2” conduits for COX. Additional conduits may be specified to support Enterprise Network Core and Data Center Locations. The size and number of conduits or sleeves used for backbone pathways depends on the usable floor space served by the backbone system. However, at least four 4 inch conduits are recommended to serve a Telecommunications Room (TR), Equipment Room (ER), or Entrance Facility (EF). (TDMM, page 6-8) Multiple Telecommunications rooms on the same floor shall be interconnected with a minimum of two 4” conduits. For horizontal station cabling, twelve inch cable tray should be substituted for conduit whenever possible. A minimum of one 4 inch EMT sleeve will be installed in all Telecommunication Rooms in order to route-in horizontal station cables. All sleeves and slots must be firestopped in accordance with applicable building codes after the cable installation is complete. If possible, sleeves, slots, and/or conduits should be located on the left side of the Telecommunications Spaces. This placement enhances the use of wall space from left to right. All conduit installed shall have the appropriate size bushings placed on the top and bottom of the sleeve to protect the cables. Interconnecting buildings in a campus environment requires a minimum of three 4” conduits. EQUIPMENT ROOM – ER (Formerly MDF): The size of the Equipment Room (ER) shall be determined as a joint effort between the Maricopa County OET Project Manager, building owner and other parties designated by MC-OET. The Equipment Room size cannot be specified until all factors relating to the work space area and equipment are considered. (TDMM, p. 6-45) 2 2 If less than 200 Work Area’s, minimum ER size = 160 ft (15m ). 2 A space with the minimum floor dimensions of 10 ft. x 16 ft. (160 ft ) should be allocated for the Equipment Room (ER) (TDMM, p. 6-43) For buildings less than 5000 square feet a room 10 ft x 8 ft may be utilized. (TDMM, p. 6-15) Provide an unobstructed clearance of a least 8’ 6” above the finished floor. The door must be at least 7’ high and 3’ wide. Doors shall have the same fire rating as the walls in the room. (TDMM, p. 6-8) Since large equipment is often located in the ER, a double door (e.g. 6 feet wide by 7.5 feet high) may be required. If building codes permit, doors should open outward to provide May 17, 2012 Document 2 - Specification & Response Document Page 352 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade additional usable space and reduce constraints on telecommunications spaces layout. Contact the Maricopa County OET Project Manager for project specific door requirements during the design phase of the project. (TDMM, p. 6-8) The rating for concentrated loading must be greater than 2000 pounds per square foot in areas that will support telecommunications equipment. The actual floor-load rating should be obtained from the building architect before construction is started. (TDMM, page 6-56) TELECOMMUNICATIONS ROOM – TR (formerly IDF): Floor Size < 5,000 ft2 >5,000 to 8,000 ft2 >8,000 to 10,000 ft2 Minimum Room Size 10 ft x 8 ft 10 ft x 9 ft 10 ft x 11 ft BONDING AND GROUNDING REQUIREMENTS General Requirements: A uniform telecommunications grounding and bonding infrastructure shall be provided for the protection of personnel and equipment conforming to all applicable codes and standards including, but not limited to the following: the current National Electric Code (NEC) Articles 250 (Grounding) and 800 (Communications Circuits), ANSI/J-STD-607-B–2011, Commercial Building Grounding (Earthing) and Bonding Requirements for Telecommunications., IEEE 1100 “Recommended Practice for Powering and Grounding Electronic Equipment”, TIA/EIA-942 “Telecommunications Infrastructure Standard for Data Centers”, and the current versions of the National Fire Protection Association (NFPA) publications NFPA 70E "Electrical Safety Requirements for Employee Workplaces", NFPA 75 "Protection of Electronic Computer/Data Processing Equipment", ANSI/NECA/BICSI-607, Telecommunications Bonding and Grounding Planning and Installation Methods for Commercial Buildings, 2010 and NFPA 780 "Lightning Protection Code". These are minimum requirements and do not replace federal, state, local, or other applicable codes, laws, or regulations which may have priority. Conflicts between this document, local safety code, BICSI guidelines, and manufacturer’s requirements should be resolved with the AHJ before proceeding. Splices in bonding or grounding conductors are not allowed. All bus bars will be located 18 inches above the floor. The elements defined by the ANSI/TIA/EIA-607-A and IEEE1100 standards are listed below: TMGB TGB TBB TBBIBC BCT Telecommunications Main Grounding Bus Bar Telecommunications Grounding Bus Bar Telecommunications Bonding Backbone Telecommunications Bonding Backbone Interconnecting Bonding Conductor Bonding Conductor for Telecommunications Telecommunications bonding to electrical ground: The Telecommunications Main Grounding Bus Bar (TMGB) will be interconnected with the building’s service equipment (power) ground using a Bonding Conductor for Telecommunications (BCT) as large as a No. 3/0 AWG. The conductor must be at least one size larger than the Telecommunications Bonding Backbone (TBB). May 17, 2012 Document 2 - Specification & Response Document Page 353 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade IMPORTANT: The TBB is a bonding conductor intended to equalize potentials between TRs on multiple floors of a building with an ultimate connection to the Entrance Facility’s (EF) TMGB. TBB installations for large sites may be too costly to achieve. As an alternative, the TGB in each TR may be bonded to the AC electrical panel for that floor of the building with a supplemental bonding connection made to the metal frame of the building, where applicable. Each of the bonding connections must be tested to verify that a low resistance connection exits. (TDMM, p. 9-19) The Telecommunications Main Grounding Bus Bar (TMGB) serves as the dedicated extension of the building grounding electrode system for telecommunications infrastructure. The TMGB also serves as the central attachment point for the Telecommunications Bonding Backbone (TBB) and equipment, and MUST be accessible to telecommunications personnel. The TMGB must be mounted as close as possible to the cable Entrance Facility (EF). (TDMM, p.9-16) The TMGB shall be:  A predrilled copper bus bar provided with standard NEMA bolt hole sizing and spacing for the type of conductor to be used.  Sized in accordance with the immediate requirements of the application and allow for the consideration of future growth.  Have a minimum dimension of ¼ in thick x 4 in wide and variable in length.  Insulated from its support; a 2" separation is recommended.  Listed by an NTRL. If the main AC service entrance panel is less than 30 feet from the TMGB, bond the TMGB to the AC grounding electrode of the panel using a bonding conductor for telecommunications (BTC). (TDMM, p.9-16) A Telecommunications Grounding Bus Bar (TGB) must be placed in each telecommunications room and equipment room and bonded by means of the telecommunications bonding backbone conductor to the Telecommunications Main Grounding Bus Bar (TMGB). The TGB should be referenced to the equipment ground terminal of the nearest AC electrical panel board to equalize potentials between them. This panel board (known as a branch circuit panel board) may reside in the ER. Also, the TGB May 17, 2012 Document 2 - Specification & Response Document Page 354 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade should be bonded to the nearest structural steel member (if available) whether it is a horizontal or vertical beam. (TDMM, pp. 8-18 and 8-19) The TGB shall:  be a predrilled copper bus bar provided with standard NEMA bolt hole sizing and spacing for the type of conductor to be used.  be sized in accordance with the immediate requirements of the application and allow for the consideration of future growth.  have a minimum dimension of ¼ in thick x 2 in wide and variable in length.  be insulated from its support; a 2" separation is recommended. The Telecommunications Bonding Backbone (TBB) cables for bonding the TGBs to the TMGB shall be sized according to length, as shown in the chart below: Sizing of the TBB TBB Length Linear M (ft) TBB Size (AWG) Less than 4 (13) 6 4 – 6 (14 – 20) 4 6 – 8 (21 – 26) 3 8 – 10 (27 – 33) 2 10 – 13 (34 – 41) 1 13 - 16 (43 – 52) 1/0 16 – 20 (53-66) 2/0 Greater than 20 (66) 3/0 All Telecommunication Rooms (TR) shall have a minimum 6 AWG bonding conductor extending from the TGB to all the racks and cabinets within the TR. This 6 AWG conductor will be referred to as the common bonding network (as referred to in TIA-942 “Telecommunications Infrastructure Standard for Data Centers”). All racks and cabinet frames will be fully bonded with paint piercing washers and bonding screws and attached to the common bonding network with a minimum 6 AWG conductor. In order to fully bond all equipment and panels to the rack, thread-forming screws must be utilized to ensure clean metal to metal contacts. SELF-TAPPING SCREWS SHOULD NEVER BE USED BECAUSE THEY CREATE METAL SHAVINGS WHICH CAN DAMAGE THE ELECTONICS. Two-hole grounding lugs will be used for the rack grounding bus bars. One-hole grounding lugs are prohibited. Each rack or cabinet shall have at least one ESD port and ESD strap provided on the front of the rack. In cases where both ends of a cable cannot be visually located at the same time, green labels shall be utilized for visual inspection of the grounding and bonding system. This labeling will be reflected on the as-built drawings referenced in the Deliverables, Section 5 of this document. May 17, 2012 Document 2 - Specification & Response Document Page 355 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade DATA CENTER GROUNDING REQUIREMENTS: Proper grounding within a data center is defined by TIA/EIA-942 “Telecommunications Infrastructure Standard for Data Centers”, J-STD-607-A, IEEE Std 1100 (IEEE Emerald Book) and BICSI TDMM Manual. The TIA/EIA-942 standard goes beyond the requirements of the National Electrical Code (NEC) to protect equipment and improve system reliability. The goals of the grounding system in a data center are to equalize electrical potentials and to create a low resistance path to ground. Five basic principles should be used when designing a grounding system to accomplish this goal, as follows: 1. 2. 3. 4. 5. The grounding system shall be intentional. The grounding system shall be visually verifiable. The grounding system shall be adequately sized. The grounding system shall direct damaging currents away from equipment. All metallic components in the data center shall be bonded to the grounding system. All bonding and grounding design and requirements shall be reviewed and approved by the Maricopa County OET Project Manager before implementation. SIGNAL REFERENCE GRID (SRG) The Signal Reference Grid has three purposes: 1. Reduce electrical noises and enhance the reliability of signal transfer across interconnected items of IT equipment. 2. Prevent circuit damage by providing a low impedance path/effective ground reference for computer room electrical equipment. 3. Minimize damage to circuits and equipment when a power system ground-fault event occurs. Best practices for the Signal Reference Grid include: 1. The SRG should be prefabricated out of #26 gauge x 2 in. wide copper strip with all crossing interconnections welded, not punched. 2. If round conductors are used, they should be at least # 6 AWG; bare copper is preferred. 3. The grid spacing of the SRG should be 2 feet, exothermically welded in the field to form a continuous grid. 4. The copper strips can be welded into a grid pattern prior to installation and then rolled out onto the floor in sections. 5. When a wire SRG is constructed using the raised floor pedestals, the flooring system must be electrically continuous. 6. Every fourth pedestal should be bonded. 7. The bonding jumper from the pedestal to the SRG should be no greater than 2 feet in length. Best practices for Rack/Cabinet grounding include: 1. All none-current-carrying metallic enclosures shall be grounded. May 17, 2012 Document 2 - Specification & Response Document Page 356 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade 2. Each equipment cabinet/rack requires its own grounding connection to the SRG. 3. A minimum of #6 AWG copper conductor mechanically terminated to the SRG and cabinet via a machine screw, through-bolt connection or factory-provided spot weld, is recommended. 4. Grounds at opposite ends of a series of racks should be attached with the framework grounding conductor going directly to the SRG. 5. Bare metal-to-metal contact is mandatory for all bonded connections, with antioxidant applied at the connection point. (BICSI Data Center Design and Best Practices, version 1.1, pp. 8-53, 8-55) SECTION 2: Horizontal Cabling All horizontal distribution cabling shall be plenum rated. Horizontal Cabling-Data/VoIP Data and VoIP applications shall utilize 4-pair, 100 ohm, CAT6 UTP, CMP cable. Horizontal Cabling-Voice Horizontal distribution supporting digital and analog voice applications shall utilize 4-pair, 100 ohm, Category 3, UTP, CMP cable. 4-pair, 100 ohm Category 5e UTP, CMP cable is an acceptable substitution. Typical services would include but not be limited to connections to legacy telephone systems, fax, elevator phone, and telephone lines for monitoring alarm systems. Cable Routing Horizontal cabling shall be installed from the workstation to the nearest floor serving TR or ER. No station cabling will run between floors. Exceptions may be required based on specific site conditions and project requirements. All exceptions must be approved in advance prior to installation and authorized in writing by the OET Project Manager. Route cabling so that a minimum distance of 12" is maintained between any network cabling and florescent lighting fixtures. Under no circumstances shall network cables be installed physically touching florescent lighting fixtures. Avoid routes that take cabling near sources of high electromagnetic radiation, electrostatic discharge, or radiated frequency (RF) interference. Devices such as electric motors or RF generating equipment may generate electrical emissions. When in doubt, check with the manufacturer of the equipment. The network may appear to function normally but problems will occur as size and network traffic increase. Cables installed in removable tile suspended ceiling areas shall not rest on the ceiling grids. Cables should be routed to provide the maximum clearance above the ceiling tiles. The Minimum clearance is at least 3 inches above the ceiling tiles. Horizontally installed cables in removable tile suspended ceiling areas will be supported by cable tray for main cable runs and J-hooks for independent cable drop locations. Where cable tray is utilized, 12 inches of clearance should be provided above the cable tray. All metal trays should be bonded back to the common bonding network as described under the Grounding and Bonding subsection of this document. May 17, 2012 Document 2 - Specification & Response Document Page 357 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Velcro shall be used at spacing of intervals of 5 feet or less. Cable bundles shall be attached with Velcro only to hangers permanently affixed to the underside of the floor above. Cable bundles may be attached to existing ceiling grid support wires provided the cable bundles do not exceed a combined per foot weight of 0.5 lb per foot. Cable may be installed using roof trusses as supports. The use of either hammer-on or screw-on beam style J-hooks is recommended. In situations where the installation of grid wire for J-hook support is being considered, consult with County Management for permission and time frame to complete this work. Existing pipes carrying liquids or gases, electrical conduits or existing cabling, shall not be used to support horizontal cables. Cable routes should not be close to any pipes or ducts which vary from ambient temperatures. Cables should be routed as high as possible above pipes and not below. Horizontal cables running parallel to electrical conduits shall not be tie-wrapped to the conduits. The network cable bundles shall be separated by a minimum of 3" of free air space from the electrical conduits. Cable pulls shall not exceed the manufacturer specifications for the pulling tension or the bend radius. The maximum pulling tension of 25 lbs as referenced by the TIA/EIA-568-B shall not be exceeded. Cable pulls shall not be stretched, crimped or compressed during installation. Pull-strings should be provided in every pathway with more than 20 cables. All horizontal or vertically installed cable that is penetrating fire walls or floor levels shall be sealed using an approved firestop compound and installed in compliance with local building codes. All fire walls will be penetrated with an elastomeric module of which one to eight can be installed with one housing frame. The elastomeric modules are specially designed to withstand the fire and hose stream test for the rated time. Frame and hardware components must be steel to survive test temperatures. An example is the Specified Technologies Incorporated EZ-Path® System Solution. All network cabling shall be installed in straight-runs parallel to building lines. When changing the direction of a cable run, a smooth 90 degree turn shall be used that adheres to the cable manufacturers minimum bend radius without kinking or damaging the cable outer jacket or conductors. The cable bend radius will not exceed 8 times the cable diameter or approximately a 2” bend radius. A service loop will be provided at each end of the cable run. The length of the service loop shall be 5 feet at the station end and 10 feet at the ER/TR end. The service loop will not overlap in a figure 8 or coil pattern within the cable or ladder tray. The cable shall be transitioned and dressed-in the cable or ladder tray. This additional length shall extend in a U-shaped, non-overlapping loop with the proper bend radius maintained. For situations where cable or ladder tray are not available or not of adequate length (e.g., Jhook installations), consult with the Maricopa County OET Project Manager. The use of a coil pattern for a service loop is prohibited. Category 6 The maximum length from the network device to the network interface at the workstation end shall not exceed 328 cable feet when using Category 6 cabling. This maximum length May 17, 2012 Document 2 - Specification & Response Document Page 358 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade includes the horizontal cable run and the patch cables installed from the switch to the patch panel and the workstation to the data jack in the faceplate. The switch to switch maximum distance shall not exceed 328 cable feet when using Category 6 cabling including any patch or line cords. The Category 6 cable shall not exceed the specifications for the specific topology being installed. The cable run shall have no splices. The cables will not be “cinched” with tie-wrap cable ties or any other device used to support the cables in the overhead ceiling space. Velcro ONLY shall be used. Due to the “crushing” effect from the weight, cable will not be run in bundles greater than 120 cables. In addition, cables should be bundled so that no more than 10 work areas are located in the same cable bundle to facilitate MAC work in the future. All terminations will follow Category 6 specifications and be Category 6 compliant. Proper termination tools will be used for the specific vendor product being installed. Patch panels and all station locations will use Panduit’s Category 6 RJ45 red or Leviton’s dark red jacks for all data drops. All cable pulls shall be labeled according to the labeling standards. All cables will be labeled approximately 6" inches from the jack. Category 3 Category 3 cabling shall be used for voice locations ONLY. Category 5e cable can be substituted if cost is less than or equal to Category 3 cable. Sites that migrate to a VOIP solution will use Category 6 cabling and those standards will apply. No more than 1 1/2 inches of outer jacket shall be removed at ANY termination point. The cable bend radius will not exceed 8 times the cable diameter. The cable run shall have no splices, “T”s, or bridge taps. Station Termination All station locations will have a single gang 4-port faceplate with two Category 6 cables and one Category 3 cable. The Category 6 cables will be terminated with Cat6 Red Panduit RJ45 or Dark Red Leviton jacks. The Category 3 cable will be terminated with two Category 3 Panduit Electric Ivory or Leviton Ivory USOC jacks. The faceplates are Electrical Ivory for Panduit and Ivory for Leviton. The TIA/EIA 568-B cabling standard will be used for cable termination. All empty ports in a faceplate will have the appropriately colored blank insert installed. Each drop location will be installed in a 1 inch EMT conduit leading back to the nearest cable tray. Each conduit will be labeled and located approximately 6 inches above the cable tray. The conduit shall contain a pull-string which ends in a 2.25 inch deep x 4 inch square box. The conduit shall enter the 2.25 inch deep x 4 inch square box from the top if the cable is coming from the ceiling and from the side if the cable is coming from a horizontal location. May 17, 2012 Document 2 - Specification & Response Document Page 359 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade No 90 degree elbows shall be used to connect the conduit to the box. A metallic cover for the box will be installed to reduce the box size to accommodate a single gang faceplate. All faceplates will be mounted level. The bottom of the faceplate will be EXACTLY 11 ½" from the floor. If the new faceplate is placed next to an existing outlet it should be placed level and square with the existing faceplate. All faceplates will be snug and tight with the wall and when mounted correctly, the faceplate will not move. A minimum of 12 inches and a maximum of 24 inches of slack should be located in the cable tray but accessible for any re-terminations required. All cables will be labeled approximately 6" inches from the jack including the patch panel end. All faceplates will be labeled as detailed in the “labeling section” in this document. ER/TR Termination A minimum of one 19” rack with vertical cable management is required in each TR or ER. The 19” rack will support all station cables terminated to Category 6 patch panels. All station cable will enter the TR/ER through 4” conduit sleeves or cable tray and will be transitioned to ladder tray to the appropriate termination location. The cable should be properly bundled with Velcro. Vertical cable managers shall be installed on both sides of the rack. Cabling shall be equally distributed to both sides of the rack. As an example: when facing the rack, cable runs 1 – 12 and 25 – 36 should be to the left side of the rack. Cable runs 13 – 24 and 37 – 48 should be to the right side of the rack. Four-inch, single-sided horizontal managers shall be installed as “pass-throughs” in the middle of the rack to provide a path for patch cables to be routed to the opposite side of the rack. Forty-eight port angled patch panels shall be used in most installations. Unused ports on the patch panels shall be plugged with a blank insert matching the color of the patch panel. Two-inch, single-sided horizontal managers may be used if approved by the Maricopa County OET Project Manager. The use of angled patch panels does not require horizontal cable managers. Waterfalls shall be installed for cable entry from the ladder tray to the vertical cable management. All station cables will maintain the same esthetics and bend radius and not overlap one another. All patch panels will have strain relief bars mounted on the rear of the rack for cable support. All Category 3 cable will be terminated on a 110-type termination block. All cable entering termination blocks must enter from the top. Cable managers will be installed with the 110-type termination block. All network cabling shall be supported by ladder tray. Copper riser cabling shall be supported by D-Rings. Where fiber and copper jumpers share the same ladder tray, the fiber shall be kept to one side and copper to the opposite side. The cable shall be properly bundled with Velcro. All 110-style punchdown blocks, cable managers and patch panels shall be mounted square and level. May 17, 2012 Document 2 - Specification & Response Document Page 360 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade The 110-type punchdown block will be used for all feeder/backbone copper and category 3 station cables. All cable shall be labeled with clear designation strips and computer or label maker printed labels. Color-codes for labeling must be adhered to. All patch panels will be labeled with label maker type labels. Backboard Layout – The following diagram provides the layout of the backboard crossconnect fields. CABLE MANAGEMENT Floor Riser 300/900 Pair 110 Tower Station Cable Cable Management 300/900 Pair 110 Tower Cable Management Qwest Feed Cable Management 300/90 0 Pair 110 Tower 300/900 Pair 110 Tower IPE Voice Cables The following colored labels will be used to identify cable termination types within the telecommunications room and is the code recommended in the TIA/EIA 606-A standard: Blue White Gray Brown Purple Green Orange Yellow Red Horizontal station cables Riser cable second level backbone or riser cable Inter-building backbone cable Common Equipment ports (IPE) Customer extension of demarcation Service provider demarcation Auxiliary circuits, alarms, security Key telephone systems LABELING Station cables shall be labeled at all termination points including the TR/ER and workstation outlet locations. A black on Yellow wrap around label will be put on each end of the cables and approximately 4-6 inches from the patch panel. Each jack at each workstation outlet shall have an individual identification number. This number shall be carried through to the TR/ER and any other points of termination that may exist. The upper and lower designation strip will be applied to the faceplate. A label machine using a 3/8” cassette tape, black on white background will be used to print the labels. Patch Panels shall be labeled using a labeling machine which prints the appropriate sized labels for the patch panel used or a label machine using a 3/8” cassette tape, black on white background. Port numbers should line up with the jack to which it is assigned. The following is an example of a wall plate with labels corresponding to patch panel labeled ports. May 17, 2012 Document 2 - Specification & Response Document Page 361 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Workstation Outlet Configuration 59 D 60 Category 6 Match Patch Panel Port Number Category 3 V 60 Match 110 Block Location Floors with more than one TR will require that the TR letter designation is added to the jack ID number (example A59 or B59). The statement of work shall reflect the closet numbering scheme used. If there is no reference in the scope of work, the Maricopa County OET Project Manager or Lead Technician shall be consulted. For ABF installations, each tube exiting the TDU shall be labeled on the tube clip organizer indicating the tube number, the LIU, and the fiber adapter panel locations. Each tube entering the LIU shall be labeled with its source information back to the TDU. Exact labeling requirements will be specified by the Maricopa County OET Project Manager. SECTION 3: Vertical Cabling All Telecommunication Rooms will have a minimum of a 50 pair copper backbone cable run from the ER. It will be terminated on a 110 style punchdown block for existing phone service. Proper grounding as described in the Bonding and Grounding Requirements in Section 1 will be adhered to for all copper backbone cabling. Circuit Protector Blocks with gas modules will be used in the ER where the transition from OSP to Plenum occurs within 50 feet of the entrance. The requirements of the NEC and local building codes must be adhered too. (TDMM, p. 5-69 states: “Chapters 7 and 8 of the NEC impose specific requirements for building backbone systems used within the United States…requirements are designed to prevent the spread of flame and smoke from floor to floor, and relate to backbone systems applicable to the ER, TR, EF, and TE...”) All TR’s will have a minimum of 24 strands of multimode fiber for network equipment connectivity. This fiber will be 50 micron Laser Optimized Fiber specified with OFS glass capable of supporting 10 gigabit to 300m (OM3) or 550m (OM4) based on the length of the fiber. All fiber installations will be Sumitomo tube cell and Air-blown fiber (ABF). For smaller installations, non-ABF fiber may be used. The Maricopa County OET Project Manager will determine which type of fiber will be installed. A service loop will be provided at each end of a fiber run. The length of the service loop will be 10 feet at each end. The proper bend radius shall be maintained. All single mode and multimode fiber will be terminated on to a rack mounted LIU unless the project warrants otherwise. The Maricopa County OET Project Manager will make that May 17, 2012 Document 2 - Specification & Response Document Page 362 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade determination. All vendor product determinations should be verified by the Maricopa County OET Program Manager or Lead Technician. All fiber terminations shall be done with LC connectors, unless otherwise noted by the Maricopa County OET Project Manager or Lead Technician. All non-ABF fiber optic cable will be installed in a protective innerduct. A plenum rating must be met if the innerduct is to be installed in a plenum environment. Check local building codes for verification. Armor protected fiber may be used in lieu of innerduct. All ABF product installations shall be done according to manufacturer and County standards by certified installers. All test results shall be done according to the warranty requirements specified by the manufacturer. All vertical cables penetrating fire walls or floor levels shall be sealed using an approved firestop compound and comply with all local building codes. Sumitomo Air Blown Fiber: All Air-Blown fiber shall be Sumitomo product and installed to Sumitomo standards by certified installers. Test results will be provided to the Maricopa County OET Project Manager upon completion of the installation. This shall be provided in a readable electronic format. The Sumitomo Future Flex Enclosure will be used by Maricopa County. An alternative for this enclosure is the Hoffman enclosure. The Maricopa County OET Project Manager will determine the size and type of enclosure used on a per installation basis. Sumitomo OSP Tube cell shall be installed in underground conduits. A Sumitomo or Hoffman waterproof enclosure 24”x12”x24” will be used in manholes and vaults (size may vary depending on location). All tube cells will be properly identified with a Plastic 2”x4” engraved label. All AFB tube cable and fiber bundle shall be installed according to the recommended installation procedures provided by Sumitomo. Some of these installation procedures are listed below. This list is not considered comprehensive and therefore does not exclude all the applicable manufacturer’s installation procedures. All tube cells shall be installed in a manner which provides the straightest route and fewest bends possible. Tight bends and sharp S-curves must be avoided. Proper reel handling and storage shall be followed for all Sumitomo tube cell cable. A visual receipt inspection of the reel and contents shall be performed. If damaged is noted, the appropriate authority shall be notified immediately. An on-reel obstruction test is strongly recommended for all tubes. Document the test results and re-seal the tube cable ends. Maximum allowable pulling tension shall be followed during any tube cable installation. Refer to the Sumitomo documentation guide for the specific pulling tension for the type of tube cell being installed. To prevent deformation of the tubes by sagging or pinch points along the route, the tube cell installation shall be done according to the installation standards provided by Sumitomo. The following installation standards are provided for a brief overview. The contractor is May 17, 2012 Document 2 - Specification & Response Document Page 363 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade responsible for ensuring all installation procedures are followed to ensure the tube cell cable is not damaged during or after installation. For cable tray installations – solid tray or tray with flat inserts in the bottom is the preferred method for TP2 tube. Ladder tray may be used if the spacing between the ladder rungs is no more than 12” apart and the rungs are at least 1” wide. Flex-wire basket tray may be used as long as the basket mesh size is no more than 4” long and 2” wide. For any trays that do not meet the above requirements, a flat insert must be inserted across the rungs or in the bottom of the tray to provide a flat and continuous support for the tube cell. Adjustable cable supports that utilize a cloth or fabric type strap ARE NOT acceptable support methods for TP2 tube cables. J-hooks by themselves are NOT acceptable methods of support. J-hooks must be spaced no more than 4-to-5 feet apart and a minimum 10 to 12 inch long piece of innerduct is placed around the tube cable as it lays in each J-hook. The innerduct must be centered in the hook to provide the best support. The tube cable shall have no more than 6” sag between the J-hooks. Plenum-rated, corrugated split innerduct shall be used. Required sizes are – Carlon Electrical Division 1-1/4” Orange, Split CF4X1-250S (or equal) for 1” OD TCO7TP2 and Carlon Electrical Division 2” Plenum-rated Orange, split CF4X10250S (or equal) for 1.7” OD TC19TP2. Ensure the “split” points upward during the installation. Velcro strapping shall be the only material used to secure TP2 Tube cable in place. However, Velcro strapping should NOT be used to support the weight of the tube cable at the narrow point load on the tubes. This will cause deformation. Nylon Tie-wraps are NEVER to be used. Appropriate support for the tube cable shall be provided when TP2 tube cable transitions on and off a cable, ladder or flex-wire tray. This support shall adhere to the installation standards provided by Sumitomo. The placement and stacking of tube cable shall be done according to the installation procedures provided by Sumitomo. Manual installation of TP2 tube cable is preferred, if pulling ropes or strings are used, a swivel should ALWAYS be used between the cable grip and the pulling rope to prevent the cable from twisting. Once the TP2 tube cable has been installed, the route should be re-inspected to correct any potential problems; add the split innerduct support if J-hooks were used; verify the sag is 6” or less and that the tube cable is not in contact with any sharp edges or points. If TC07TP2 is used, verify the cable is laying on the flat surface and not the points. All tube cells will be supported with Kellems Grips for bottom tube entries and plastic bushings on top of enclosure. Hose Clamps are not acceptable to MC-OET to support Tube cells in the enclosure even if Sumitomo would warranty it. All tube cells will be supported with appropriate 1-hole C-Clamps or D-rings to provide support as the tube exits the conduit and enters the TDU. Care should be taken to obtain the proper size clamp or D-ring so the tube cells do not get damaged. All Sumitomo fiber bundles that are to be uninstalled shall be removed following the proper procedures outlined by Sumitomo. The fiber bundle shall be re-rolled on an appropriate size reel as specified by the Sumitomo standards. May 17, 2012 Document 2 - Specification & Response Document Page 364 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade All Sumitomo tube cell cables in stock shall be stored according to the Sumitomo standards. SECTION 4: Testing All technicians shall be trained and certified by the manufacturer or a designated representative of the manufacturer on the testing equipment used. An electronic version of the test results in PDF file format shall be submitted to the “Office of Enterprise Technology” as part of the deliverables listed in Section 5. Test results from major projects shall be submitted on “readable” CDs. Final test submittals shall not include failing test results. Cables that fail testing shall be repaired or replaced and re-tested until 100 percent of the cabling passes all testing. A. Horizontal Copper Cabling 1. CATEGORY 5E AND 6 horizontal cabling shall be tested as recommended in the ANSI/EIA/TIA 586-C.2 Telecommunications Standard. 2. The installed twisted-pair horizontal links shall be tested from the IDF in the telecommunications room to the telecommunication wall outlet in the work area for compliance with the “Permanent Link” performance specification as defined in the TIA CATEGORY 5E AND 6 Standard using a Fluke DTX CableAnalyzer Series cable tester or County approved test equipment in compliance with ANSI/TIA-1152. 3. Submit detailed test results in electronic media in PDF file format. B. Optical Fiber Cabling 1. Initially test optical cable with a light source and power meter utilizing procedures as stated in ANSI/TIA/EIA-526-14A: OFSTP-14A Optical Power Loss Measurements of Installed Multimode Fiber Cable Plant and ANSI/TIA/EIA-526-7 Measurement of Optical Power Loss of Installed Single mode Fiber Cable Plant. Measured results shall be plus/minus 1 dB of submitted loss budget calculations. If loss figures are outside this range, test cable with optical time domain reflectometer to determine cause of variation. 2. Cables shall be tested at 850 and 1300 nm for multimode optical fiber cables. Cables shall be tested at 1310 and 1550 nm for single mode optical fibers. 3. Testing procedures shall utilize “Method B” – One jumper reference. 4. Bi-directional testing of optical fibers is required. 5. Submit detailed test results in electronic media in PDF file format. Voice cables shall be tested with a mod-tap tester. Software related to the specific cable tester used must be provided to MC-OET by the Contractor so that the test results can be read (readable format). Copper Riser cable tests shall be from the TR termination blocks or patch panels to the ER termination blocks or patch panels. A continuity test is required upon completion of the installation. Final System Test results of riser cabling shall be documented and provided to the “Office of Enterprise Technology” at final acceptance of the completed project, along with as-built May 17, 2012 Document 2 - Specification & Response Document Page 365 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade drawings and other required documentation. This shall be provided in a readable electronic format. All fiber optic cable strands shall be tested using a calibrated fiber tester approved by the Maricopa County OET Project Manager prior to installation to ensure all strands are continuous and match published specifications. If calibration is required for the tester, verification must be provided upon request. All terminated fiber optic cable strands shall be tested using calibrated fiber testers approved by the Maricopa County OET Project Manager. The maximum db loss per strand is as follows: ST Connector .2db SC Connectors .2db LC Connectors .2db For non-ABF fiber, defective strands revealed in the testing procedure will be repaired and or replaced prior to final acceptance of the completed project. Repair of existing fiber that has been damaged, may be done with a Fusion Splice. No Mechanical splices will be accepted. All splices will be installed in the appropriate enclosures per factory specifications. Fusion splices may not be done on ABF fiber bundles. Electronic files or a CD containing the test results shall be used to verify the fiber optic testing. The test results will be turned-in to the “Office of Enterprise Technology” at final acceptance of the completed project, along with as-built drawings and other required documentation. Any strands that failed shall be repaired or replaced and re-tested. For major projects, a designated individual from the Communication Installation Vendor shall work with the Panduit, Leviton or Sumitomo factory representatives to obtain the Warranty as part of the close out documentation. This should be completed within 60 days of the completion of the project. An e-mail shall be sent to the manufacturer or vendor representative to schedule a walk-through. The Maricopa County OET Project Manager and designated Lead Technician shall be copied on the e-mail request. All Sumitomo Tube Cell and Fiber Bundle installations shall be documented and tested. Each cell tube number and the location it is going too shall be documented on an as-built drawing. The tube pressure and obstruction test results shall be recorded once the installation has been completed. This documentation should be done according to the warranty requirements of the manufacturer responsible for issuing the warranty. Fiber bundle test results for each strand shall be provided in the format required by the manufacturer responsible for issuing the warranty. SECTION 5: Deliverables As-Built Drawings Upon completion of a project, it is required that the Contractor’s Lead Technician provide/return to Maricopa County Telecommunications Department/Office of Enterprise Technology, all floor plans or drawings related to the project showing the following information at a minimum: a. Horizontal cable routes for drops and tube cell cable, or non-ABF fiber. b. Vertical cable routes for feeder cable, tube cell cable, or non-ABF Fiber. May 17, 2012 Document 2 - Specification & Response Document Page 366 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade c. Office drop locations with drop numbers per labeling standards provided in Section One. d. ER/TR details showing location and layout of termination blocks. e. Locations of vertical conduits or between floor vertical accesses. f. Locations and size of horizontal conduits and junction boxes if home run conduits are used for containment of network cabling. g. Labeling and placement of Sumitomo ABF TDU, clear tube runs and LIUs. h. Locations of ground wire and bus bar(s). i. Service provider entrance to building. j. Notation of vendor product used for Layer 1 installation (Panduit, Leviton) and fiber installations. k Additional information specific to the installation may be required by the Maricopa County OET Project Manager. As-built drawings shall be submitted in electronic format using CAD software in DWG file format. Hard copies shall be available upon request. Test Results Test results shall be provided in a readable electronic format for all cable runs and fiber installations. Test results in the format required for the warranty shall be provided for the Sumitomo tube cell cable pressure test; obstruction test and fiber bundle test. A copy of the test results shall be included as part of the deliverables provided to MC-OET. Warranty For major projects, a designated individual from The Communication Installation Vendor shall work with the Panduit, Leviton or Sumitomo factory representatives to obtain the Warranty as part of the close-out documentation. This should be completed within 60 days of the completion of the project. An email shall be sent to the manufacturer or vendor representative to schedule a walk-through. The Maricopa County OET Project Manager and designated Lead Technician shall be copied on the e-mail request. All locations where communications cabling must penetrate floors, firewalls or drywall above the ceiling grid shall be sleeved and fire sealed using an approved firestop system. 11. PINNING. b. T568B pinning standard will be utilized on all copper cable terminations. SECTION 6: Parts List Cabling material from two (2) manufacturers (Leviton and Panduit) are utilized in the current campus infrastructure for Maricopa County. A list of commonly used parts is shown below. Items not listed require written MC-OET approval prior to installation. May 17, 2012 Document 2 - Specification & Response Document Page 367 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade PANDUIT VENDOR Part # DESCRIPTION PANDUIT CFPL2EIY FACEPLATE, SG 2 PORT PANDUIT CFPL4EIY FACEPLATE, SG 4 PORT PANDUIT CJ688TGRD RJ45, CAT6 INSERT – RED PANDUIT CJ66UEIY C3 USOC INSERT – ELECTRIC IVORY PANDUIT CMBBL-X INSERT BLANK BLK PANDUIT CMBEI-X INSERT BLANK EIV PANDUIT CMWB WATERFALL BASE-LADDER RACK PANDUIT CMRPSH20 20 AMP HORIZONTAL POWER STRIP PANDUIT CMRPSH15 15 AMP HORIZONTAL POWER STRIP PANDUIT PRD8 DUAL HINGED METAL DOOR PANDUIT PRV8 8"WX84", VERT FRONT REAR MGR PANDUIT UICMPP48BLY 48P FLAT MODULAR C6 PATCH PANEL PANDUIT UICMPPA48BLY 48P ANGELED MODULAR C6 PATCH PANEL PANDUIT NCMHF2 2 RU FRONT ONLY HORIZONTAL CABLE MANAGER PANDUIT NCMHAEF2 HORIZONTAL WIRE MGR 2RU HINGED DOOR (PASS THRUs) PANDUIT NCMHAEF4 HORIZONTAL WIRE MGR 4RU HINGED DOOR (PASS THRUs) PANDUIT DP485E88TGY FLAT CAT5e 48 PORT PATCH PANEL 110 PUNCHDOWN PANDUIT KWP5EY WALL PHONE JACK AND PLATE PANDUIT FAP6WAQDLC FAP (6) AQUA LC DUPLEX (10GIG) PANDUIT FAP6WEIDLC FO ADAPTER PANEL 6PACK W MM LC Duplex EIV COUPLERS PANDUIT FAP6WBUDLCZ FO ADAPTER PANEL 6PACK W SM LC PANDUIT FLCSMEIY 50 MICRON LC CONN-FLD POLISH PANDUIT FLCSSBUY LC SM CERAMIC ANAER PANDUIT FCE1U 1RU FIBER ENCLOSURE PANDUIT FCE4U 4RU FIBER ENCLOSURE PANDUIT P110KB1004Y 110 BLOCK 100 PR 4PR - CAT5E KIT PANDUIT P110KB1005Y 110 BLOCK 100 PR 5PR - CAT5E KIT PANDUIT P110JTW-X JUMPER TROUGH WITH LEGS PANDUIT P110KT3005Y 110 BLOCKI 300PR TOWER PANDUIT P110KT9005Y 110 BLOCK 900PR TOWER PANDUIT P110JT-X JUMPER TROUGH WITHOUT LEGS PANDUIT P110B100-X 110 BLOCK 100 PR W/O LEGS FOR TOWER PANDUIT P110CB4-XY C4 CLIPS – 10/PKG PANDUIT P110CB5-XY C5 CLIPS – 10/PKG PANDUIT PLT2S-M 7 1/2 CABLE TIES PANDUIT PLT3S-M 11 1/2" CABLE TIES PANDUIT PLT4S-M 14 1/2" CABLE TIES PANDUIT JBX3510EI-A JUNCT BOX BASE/COVER PANDUIT LD5EI6-A 6’ ELECTRICAL IVORY SURFACE RACEWAY PANDUIT CF5EI-E COUPLER FITTING PANDUIT RAF5EI-E RIGHT ANGLE FITTING May 17, 2012 Document 2 - Specification & Response Document Page 368 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade PANDUIT ICF5EI-E INSIDE CORNER FITTING PANDUIT OCF5EI-E OUTSIDE CORNER FITTING PANDUIT TF5EI-E TEE FITTING PANDUIT ECF5EI-E END CAP PANDUIT DCF5EI-X DROP CEILING FITTING PANDUIT LD10EI6-A 6’ ELECTRICAL IVORY SURFACE RACEWAY PANDUIT CF10EI-X COUPLER FITTING PANDUIT RAF10EI-X RIGHT ANGLE FITTING PANDUIT ICF10EI-X INSIDE CORNER FITTING PANDUIT OCF10EI-X OUTSIDE CORNER FITTING PANDUIT TF10EI-X TEE FITTING PANDUIT ECF10EI-X END CAP PANDUIT DCF10EI-X DROP CEILING FITTING PANDUIT S100X150YIJ LAMINATED YELLOW LABELS (2500/PKG) 50M MM FIBER JUMPERS PANDUIT F5D3-3M1Y 1M 50 MICRON SC-SC FIBER JUMPER PANDUIT F5D3-3M10Y 10M 50 MICRON SC-SC FIBER JUMPER PANDUIT F5D3-3M2Y 2M 50 MICRON SC-SC FIBER JUMPER PANDUIT F5D3-3M3Y 3M 50 MICRON SC-SC FIBER JUMPER PANDUIT F5D3-3M5Y 5M 50 MICRON SC-SC FIBER JUMPER PANDUIT F5D3-3M7Y 7M 50 MICRON SC-SC FIBER JUMPER PANDUIT F5E3-10M1Y 1M 50 MICRON SC-LC FIBER JUMPER PANDUIT F5E3-10M10Y 10M 50 MICRON SC-LC FIBER JUMPER PANDUIT F5E3-10M2Y 2M 50 MICRON SC-LC FIBER JUMPER PANDUIT F5E3-10M3Y 3M 50 MICRON SC-LC FIBER JUMPER PANDUIT F5E3-10M5Y 5M 50 MICRON SC-LC FIBER JUMPER PANDUIT F5E3-10M7Y 7M 50 MICRON SC-LC FIBER JUMPER PANDUIT F5F10-10M1Y 1M 50 MICRON LC-LC FIBER JUMPER PANDUIT F5F10-10M10Y 10M 50 MICRON LC-LC FIBER JUMPER PANDUIT F5F10-10M2Y 2M 50 MICRON LC-LC FIBER JUMPER PANDUIT F5F10-10M3Y 3M 50 MICRON LC-LC FIBER JUMPER PANDUIT F5F10-10M5Y 5M 50 MICRON LC-LC FIBER JUMPER 50M MM 10GIG FIBER JUMPERS PANDUIT FXE3-10M2Y 2M 50M MM AQUA SC TO LC FIBER JUMPER PANDUIT FXE3-10M3Y 3M 50 MM AQUA SC TO LC FIBER JUMPER PANDUIT FXE3-10M5Y 5M 50 MM AQUA SC TO LC FIBER JUMPER PANDUIT FXE3-10M7Y 7M 50 MM AQUA SC TO LC FIBER JUMPER PANDUIT FXE3-10M10Y 10M 50 MM AQUA SC TO LC FIBER JUMPER PANDUIT FXE10-10M2Y 2M 50M MM Aqua LC to LC FIBER JUMPER PANDUIT FXE10-10M3Y 3M 50M MM Aqua LC to LC FIBER JUMPER May 17, 2012 Document 2 - Specification & Response Document Page 369 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade PANDUIT FXE10-10M5Y 5M 50M MM Aqua LC to LC FIBER JUMPER PANDUIT FXE10-10M7Y 7M 50M MM Aqua LC to LC FIBER JUMPER PANDUIT FXE10-10M10Y 10M 50M MM Aqua LC to LC FIBER JUMPER PANDUIT F9E3-10M2Y 2M Single Mode SC to LC FIBER JUMPER PANDUIT F9E3-10M3Y 3M Single Mode SC to LC FIBER JUMPER PANDUIT F9E3-10M5Y 5M Single Mode SC to LC FIBER JUMPER PANDUIT F9E3-10M7Y 7M Single Mode SC to LC FIBER JUMPER PANDUIT F9E3-10M10Y 10M Single Mode SC to LC FIBER JUMPER PANDUIT F9E10-10M2Y 2M Single Mode LC to LC FIBER JUMPER PANDUIT F9E10-10M3Y 3M Single Mode LC to LC FIBER JUMPER PANDUIT F9E10-10M5Y 5M Single Mode LC to LC FIBER JUMPER PANDUIT F9E10-10M7Y 7M Single Mode LC to LC FIBER JUMPER PANDUIT F9E10-10M10Y 10M Single Mode LC to LC FIBER JUMPER SINGLE MODE COPPER PATCH CABLES – all patch cables should be ordered WITHOUT Boots! PANDUIT UTPSP8BLY 8' C6 BLACK PATCH CORD PANDUIT UTPSP10BLY 10' C6 BLACK PATCH CORD PANDUIT UTPSP8GRY 8' C6 GREEN PATCH CORD PANDUIT UTPSP10GRY 10' C6 GREEN PATCH CORD PANDUIT UTPSP15GRY 15' C6 GREEN PATCH CORD PANDUIT UTPSP20GRY 20' C6 GREEN PATCH CORD PANDUIT UTPSP7YLY 7' C6 YELLOW PATCH CORD PANDUIT UTPSP10YLY 10' C6 YELLOW PATCH CORD PANDUIT UTPSP15YLY 15' C6 YELLOW PATCH CORD PANDUIT UTPSP20YLY 20' C6 YELLOW PATCH CORD PANDUIT UTPSP25YLY 25' C6 YELLOW PATCH CORD PANDUIT UTPSP7Y 7' C6 WHITE PATCH CORD PANDUIT UTPSP10Y 10' C6 WHITE PATCH CORD PANDUIT UTPSP15Y 15' C6 WHITE PATCH CORD SUMITOMO BE03DW BLACK DRIVE WHEELS-SET SUMITOMO BE03SL BLACK RUBBER AIR SEAL SUMITOMO BE3MFT BLACK BLOWING TIP THREADED SUMITOMO BEBB01 TEST BEADS 100 COUNT – 5MM SUMITOMO BEBB40P TEST BEADS 100 COUNT – 4MM SUMITOMO DE20IDU ABF ENCLOSURE 20HX20WX7D SUMITOMO DE08MA GRAY QR END CAP 10 PK SUMITOMO DE08MB BRASS BULKHEAD QR COUP SUMITOMO DE06MP ORANGE TUBE PLUGS 10/PK - 6MM SUMITOMO DE08MC2 CLEAR PLASTIC QR COUPL SUMITOMO ABF May 17, 2012 Document 2 - Specification & Response Document Page 370 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade SUMITOMO DE08MT BLACK T-COUPLING SUMITOMO DETC008 TUBE CLIP ORGANIZER SUMITOMO DETCTB ABF TUBE ORGANIZER SUMITOMO FT3MFB RUBBER FIBER BUSHINGS – tube plugs SUMITOMO BETC001 TUBE CUTTER SUMITOMO BETC00B REPLACEMENT BLADE FOR ABOVE CUTTER SUMITOMO FB18SX 18 STRAND SINGLE MODE FIBER SUMITOMO FB24SX 24 STRAND SM FIBER SUMITOMO FB18M5 18 STRAND MM 50M FIBER (STANDARD) SUMITOMO FB18G53 18 STRAND MM 50M FIBER (LASER OPTIMIZED) SUMITOMO FB24G53 24 STRAND MM 50M FIBER (LASER OPTIMIZED) SUMITOMO FB24M5 24 STR 50 MICRON FIBER (STANDARD) SUMITOMO FTFLD18 18-FIBER BUNDLE BREAKOUT KIT SUMITOMO FTFLD24 24-FIBER BUNDLE BREAKOUT KIT SUMITOMO TC01TXX TRANSLUCENT TUBE-NON FLAME SUMITOMO TC07TP2 7T OFNP 1JKT PLENUM RATED TUBE (1.0 OD) SUMITOMO TC19TP2 19T OFNP 1JKT PLENUM RATED TUBES (1.7 OD) SUMITOMO TC07TR3 7T OFNR 2 JKT RISER (1.3 OD) SUMITOMO TC19TR3 19T OFNR 2JKT RISER (1.9 OD) Dust-Tight Kellems Strain Relief Grips (for liquid tight – consult SEL specs) HUBBELL 73031211 STRAIN RELIEF DELUXE CORD GRIP 1.0 OD (Plenum 7 tube) HUBBELL 73031212 DELUXE CORD GRIP 1.3 OD (Riser 7 tube) HUBBELL 73031214 DELUXE CORD GRIP 1.7 OD (Plenum 19 tube) HUBBELL 73031214 DELUXE CORD GRIP 1.9 OD (for riser 19 tube) FIBER SUPPLIES SYMX 700006737 8.5x11" Type A Brown FO Polish paper w foam back (100PK) SYMX 700006711 8.5x11" Type D Green FO Polish paper (100Pk) FISA 680 FO Adhesive Anaerobic Bottle (ea) FISA 7649 FO Primer Bottle (ea) LEVITON VENDOR VENDOR PART # DESCRIPTION LEVITON 49255-H24 24 PORT FLAT PATCH PANEL LEVITON 49255-H48 48 PORT FLAT PATCH PANEL LEVITON 49256-H48 48 PORT ANGLED PATCH PANEL - EMPTY PANDUIT SRB19BLY 19” STRAIN RELIEF BAR – BLACK (Need 2 for 48 port patch panels) LEVITON 5500-192 20 AMP HORIZONTAL POWER STRIP NEMA 5-20P INPUT PLUG – NEMA 5-20R RECEPTICLES LEVITON 5500-190 15 AMP HORIZONTAL POWER STRIP NEMA 5-15P INPUT PLUG – NEMA 5-15R RECEPTICLES LEVITON 42080-2IS SINGLE GANG 2 PORT FACEPLATE IVORY – W ID WINDOW LEVITON 42080-4IS SINGLE GANG 4 PORT FACEPLATE IVORY – W ID WINDOW May 17, 2012 Document 2 - Specification & Response Document Page 371 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade LEVITON 61110-RR6 DARK RED CAT6 SINGLE JACK LEVITON 61110-BR6 DARK RED CAT6 BULK PACKAGE – 25 – purchase when require multiples of 25 for quantity LEVITON 41108-RI3 CAT3 USOC IVORY JACK LEVITON 41084-BEB BLANK INSERT – BLACK LEVITON 41084-BIB BLANK INSERT – IVORY LEVITON 5F100-12A 6-PACK DUPLEX LC MM (12 fiber) 10 GIG AQUA, ZIRCONIA CERMIC SLEEVE LEVITON 5F100-12P 6-PACK DUPLEX LC MM (12 fiber) IVORY,PHOSPHORUS BRONZE SLEEVE LEVITON 5F100-12Z 6-PACK DUPLEX LC SM (12 fiber) BLUE, ZIRCONIA CERMIC SLEEVE LEVITON 5R2UH-S06 OPT-X ULTRA 2RU FIBER ENCLOSURE (holds 6 plates) LEVITON 5R4UH-S12 OPT-X ULTRA 4RU FIBER ENCLOSURE (holds 12 plates) LEVITON 49990-MDL FAST CURE LC CONNECTOR – MM 50 MICRON FIELD POLISH .9 MM BOOT LEVITON 49990-SDL FAST CURE LC CONNECTOR – SM FIELD POLISH .9 MM BOOT FIBER PATCH CABLES – 50M MULTIMODE LEVITON 5LDCL-M01 1M 50 MICRON 10GIG SC-LC FIBER JUMPER (Aqua) LEVITON 5LDCL-M02 2M 50 MICRON 10GIG SC-LC FIBER JUMPER (Aqua) LEVITON 5LDCL-M03 3M 50 MICRON 10GIG SC-LC FIBER JUMPER (Aqua) LEVITON 5LDCL-M05 5M 50 MICRON 10GIG SC-LC FIBER JUMPER (Aqua) LEVITON 5LDCL-M07 7M 50 MICRON 10GIG SC-LC FIBER JUMPER (Aqua) – NOT STANDARD LENGTH LEVITON 5LDCL-M10 10M 50 MICRON 10GIG SC-LC FIBER JUMPER (Aqua) LEVITON 5LDLC-M01 1M 50 MICRON AQUA LC-LC FIBER JUMPER (Aqua) LEVITON 5LDLC-M02 2M 50 MICRON AQUA LC-LC FIBER JUMPER (Aqua) LEVITON 5LDLC-M03 3M 50 MICRON AQUA LC-LC FIBER JUMPER (Aqua) LEVITON 5LDLC-M05 5M 50 MICRON AQUA LC-LC FIBER JUMPER (Aqua) LEVITON 5LDLC-M07 7M 50 MICRON AQUA LC-LC FIBER JUMPER (Aqua) - NOT STANDARD LENGTH LEVITON 5LDLC-M10 10M 50 MICRON AQUA LC-LC FIBER JUMPER (Aqua) LEVITON 5LDSC-M01 1M 50 MICRON AQUA SC-SC FIBER JUMPER (Aqua) LEVITON 5LDSC-M02 2M 50 MICRON AQUA SC-SC FIBER JUMPER (Aqua) LEVITON 5LDSC-M03 3M 50 MICRON AQUA SC-SC FIBER JUMPER (Aqua) LEVITON 5LDSC-M05 5M 50 MICRON AQUA SC-SC FIBER JUMPER (Aqua) LEVITON 5LDSC-M07 7M 50 MICRON AQUA SC-SC FIBER JUMPER (Aqua) - NOT STANDARD LENGTH 5LDSC-M10 10M 50 MICRON AQUA SC-SC FIBER JUMPER (Aqua) LEVITON SINGLE MODE LEVITON UPDCL-S01 1M SINGLE MODE SC-LC FIBER JUMPER LEVITON UPDCL-S02 2M SINGLE MODE SC-LC FIBER JUMPER LEVITON UPDCL-S03 3M SINGLE MODE SC-LC FIBER JUMPER LEVITON UPDCL-S05 5M SINGLE MODE SC-LC FIBER JUMPER LEVITON UPDCL-S07 7M SINGLE MODE SC-LC FIBER JUMPER- NOT STANDARD LENGTH LEVITON UPDCL-S10 10M SINGLE MODE SC-LC FIBER JUMPER LEVITON UPDLC-S01 1M SINGLE MODE LC-LC FIBER JUMPER LEVITON UPDLC-S02 2M SINGLE MODE LC-LC FIBER JUMPER LEVITON UPDLC-S03 3M SINGLE MODE LC-LC FIBER JUMPER May 17, 2012 Document 2 - Specification & Response Document Page 372 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade LEVITON UPDLC-S05 5M SINGLE MODE LC-LC FIBER JUMPER LEVITON UPDLC-S07 7M SINGLE MODE LC-LC FIBER JUMPER- NOT STANDARD LENGTH LEVITON UPDLC-S10 10M SINGLE MODE LC-LC FIBER JUMPER LEVITON UPDSC-S01 1M SINGLE MODE SC-SC FIBER JUMPER LEVITON UPDSC-S02 2M SINGLE MODE SC-SC FIBER JUMPER LEVITON UPDSC-S03 3M SINGLE MODE SC-SC FIBER JUMPER LEVITON UPDSC-S05 5M SINGLE MODE SC-SC FIBER JUMPER LEVITON UPDSC-S07 7M SINGLE MODE SC-SC FIBER JUMPER- NOT STANDARD LENGTH LEVITON UPDSC-S10 10M SINGLE MODE SC-SC FIBER JUMPER COPPER PATCH CABLES – all patch cables shall be ordered with NO Boots! LEVITON 6D460-05W 5’ CAT6 WHITE PATCH CORD – NO BOOTS LEVITON 6D460-07W 7’ CAT6 WHITE PATCH CORD – NO BOOTS LEVITON 6D460-10W 10’ CAT6 WHITE PATCH CORD – NO BOOTS LEVITON 6D460-15W 15’ CAT6 WHITE PATCH CORD – NO BOOTS LEVITON 6D460-20W 20’ CAT6 WHITE PATCH CORD – NO BOOTS LEVITON 6D460-05Y 5’ CAT6 YELLOW PATCH CORD – NO BOOTS LEVITON 6D460-07Y 7’ CAT6 YELLOW PATCH CORD – NO BOOTS LEVITON 6D460-10Y 10’ CAT6 YELLOW PATCH CORD – NO BOOTS LEVITON 6D460-15Y 15’ CAT6 YELLOW PATCH CORD – NO BOOTS LEVITON 6D460-20Y 20’ CAT6 YELLOW PATCH CORD – NO BOOTS LEVITON 6D460-05G 5’ CAT6 GREEN PATCH CORD – NO BOOTS LEVITON 6D460-07G 7’ CAT6 GREEN PATCH CORD – NO BOOTS LEVITON 6D460-10G 10’ CAT6 GREEN PATCH CORD – NO BOOTS LEVITON 6D460-15G 15’ CAT6 GREEN PATCH CORD – NO BOOTS LEVITON 6D460-20G 20’ CAT6 GREEN PATCH CORD – NO BOOTS LEVITON 6D460-07E 7’ CAT6 BLACK PATCH CORD – NO BOOTS LEVITON 6D460-10E 10’ CAT6 BLACK PATCH CORD – NO BOOTS LEVITON 6D460-15E 15’ CAT6 BLACK PATCH CORD – NO BOOTS LEVITON 6D460-20E 20’ CAT6 BLACK PATCH CORD – NO BOOTS LEVITON 41AB2-1F4 110 Block 100 Pr w legs - 5e C4 Kit LEVITON 41AB2-1F5 110 Block 100 Pr w legs - 5e C5 Kit LEVITON 41MB2-3F4 110 BLOCK 300PR TOWER LEVITON 41A10-HCM 110 JUMPER TROUGH W/LEGS VENDOR VENDOR PART # DESCRIPTION CPI 55053-703 19”X7’ STANDARD RACK - BLACK CPI 10595-712 BLACK 12” RACK MOUNTING PLATE CPI 11421-712 WALL ANGLE SUPPORT KIT FOR 12” LADDER - BLACK CPI 10610-019 19”RACK HORIZONTAL BUSBAR CPI 10250-712 12” UNIVERSAL CABLE RUNWAY-BLACK CPI May 17, 2012 Document 2 - Specification & Response Document Page 373 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade CPI 10642-001 END CAP 1.5X3/8 BLACK CPI 11301-001 BUTT-SPLICE KIT - GOLD CPI 11302-001 JUNCTION SPLICE – 90 DEGREE - GOLD CPI 11312-712 BLACK 12” TRIANGULAR SUPPORT BRACKET CPI 12833-703 GLOBAL SINGLE SIDED VERTICAL CABLE MANAGER – BLACK 7’Hx6”Wx9.3”D (need 2 for 1 rack) CPI 12836-702 CABLE RINGS FOR GVCS – SET OF 7 (Use for back side of vertical cable management) CPI 12100-706 CABLE RADIUS DROP – FOR CROSS MEMBER ATTACHMENT – 5” WIDE -BLACK CPI 12101-703 CABLE RADIUS DROP – FOR STRINGER ATTACHMENT – 5” WIDE -BLACK CPI 40153-012 TMGB – BUSBAR 4”W x 1/4”H x 12”L (Used in ER (MDFs) CPI 13622-012 TGB – BUSBAR 2”W x 1/4"H x 12”L (Used in TC (IDFs) CPI 30130-719 19” 2RU 5” DEEP HORIZONTAL CABLE MANAGER – SINGLE SIDED - BLACK CPI TS1004331 19” SINGLE SIDED BLACK 4 RU HORIZONTAL CABLE MANAGER MISCELLANEOUS PARTS VENDOR VENDOR PART # DESCRIPTION 3M 80610551105 ELECTRICAL TAPE 3M 98040054177 FIREPUTTY HILTI 378287 2” FIRE BARRIER MUFFIN HILTI 378288 4” FIRE BARRIER MUFFIN STI EZDP33FWS FIRE BARRIER SLEEVE B-Line BCH32-W2 2" J HOOK GARV PL-230-CSC BUCKET OF 6500# JETLINE CADDY MPLS METAL SINGLE GANG MOUNTING PLATE BRACKET W DRYWALL SCREWS 189645 25 YARD ROLL VELCRO AMIN 12590 6 GA STRANDED GREEN GROUNDING WIRE BURNDY YA6CL2 1880ENA1/NSC12 2 HOLE GROUND LUGS CIRCA CIRCA 1880ENA1-NSC25 1880ENA1-NSC50 1880ENA1-NSC100 CIRCA 3B1E CIRCA CIRCA 12/PR PROTECTOR 110 STYLE 25/PR PROTECTOR 110 STYLE 50/PR PROTECTOR 110 STYLE 100/PR PROTECTOR 110 STYLE GAS MODULES Boxed Cable (1000’) SUPERIOR 66-246-4B 4 PR 23 AWG CAT6 CABLE - CMP WHITE SUPERIOR 18-241-46 4 PR 24AWG CAT3 CABLE - CMP WHITE GENERAL 7131901 4 PR 23AWG CAT6 CABLE - CMP WHITE GENERAL 2131245 PR 24AWG CAT3 CABLE - CMP WHITE May 17, 2012 Document 2 - Specification & Response Document Page 374 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade PARTS LIST FOR DATA CENTER BUILDOUT – Downtown and Disaster Recovery Site VENDOR VENDOR PART # DESCRIPTION PANDUIT CRS4-125-X STACKABLE CABLE RACK SPACERS PANDUIT DPFP1 BLANK PANEL FILLER 1 RU 19” PANDUIT DPFP2 BLANK PANEL FILLER 2 RU 19” PANDUIT DPFP4 BLANK PANEL FILLER 4 RU 19” PANDUIT FRBC6X4YL YELLOW 6X4 COUPLER PANDUIT FREC6X4YL END FITTING 6X4 YELLOW PANDUIT FRFWCSC6YL SPLT COVER FOR 4-WAY HORIZ YELLOW PANDUIT FRFWC6X4YL 4-WAY CROSS FITTING 6X4 PANDUIT FRRASC6YL SPLIT COVER FOR RIGHT ANGLE (90 Degree) FITTING YELLOW PANDUIT FRRA6X4YL RIGHT ANGLE (90 Degree) FITTING 6X4 YELLOW PANDUIT FRHC6YL6 DUCT COVER 6X4 6' YELLOW PANDUIT FRT6X4YL HORIZONTAL TEE 6X4 YELLOW PANDUIT FRTSC6X4YL SPLIT COVER FOR HORIZONTAL TEE 6X4 YELLOW PANDUIT FRVT6X4YL TEE 6" VERT YELLOW PANDUIT FR6ALB LADDER BRACKET 6" ADJUSTABLE – FOR TROUGH PANDUIT FR6X4YL6 DUCT SOLID 6X4 6' YELLOW TROUGH (6’ lengths) PANDUIT FRHC6YL6 SNAP-ON HINGED COVER FOR TROUGH (6’ lengths) PANDUIT FR6TRBN58 Quick Lock Bracket for 5/8 all thread (used at DR site for Translucent tube support) LEVITON 6D460-50L 50’ CAT6 SOLID CMR PATCH CORD WITH MODULAR PLUG AND NO BOOTS (use for cross connect) PANDUIT UPBU50Y C6 SOLID CMR W/TX6 MOD PLUG (data center- USE ONLY) CPI TS1004331 4RU UNIVERSAL HORIZONTAL CABLE MANAGER 19” WIDE – HINGED SNAP-ON COVER - BLACK LEVITON 49254-BP1 1RU BLANK FILLER PANEL – 19” BLACK LEVITON 49254-BP2 2RU BLANK FILLER PANEL – 19” BLACK LEVITON 49254-BP4 4RU BLANK FILLER PANEL – 19” BLACK LEVITON 34537-000 SNAP IN FILLER PANEL 1U 1 PC (server cabinets only – cage nut rails) LEVITON 34537-001 SNAP IN FILLER PANEL 1U 6 PC (server cabinets only – cage nut rails) LEVITON 34538-000 SNAP IN FILLER PANEL 2U 1 PC (server cabinets only – cage nut rails) LEVITON 34538-001 SNAP IN FILLER PANEL 2U 6PC (server cabinets only – cage nut rails) CPI 55053-703 19”X7’ DISTRIBUTION RACK CPI TS1005742 T2 CABINET FOR HIGH DENSITY SERVERS – BLACK CPI TS1005701 T2 CABINET FOR HOT/COLD AISLE – SERVERS – BLACK CPI 34434-C01 PDU MOUNTING BRACKET FOR 6509 SWITCH CABINETS – need purchase 1 additional for mounting second power strip in each cabinet CPI 10596-708 CABLE RETAINING POST – 8” HIGH BLACK W END CAPS – use for cable row management CPI 10250-724 24” LADDER TRAY - BLACK CPI 11421-724 24” WALL ANGLE SUPPORT KIT - BLACK CPI 13392-712 PATH DIVIDER FOR LADDER TRAY – BLACK May 17, 2012 Document 2 - Specification & Response Document Page 375 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade CPI DP3082364 6509 Switch Cabinet with cable Management fingers/exhaust duct (for DR site) CPI 34434-C01 Power strip mounting bracket (need to order one for each cabinet – if use APC 7983 PDU) Note: Vertical cable management for the racks will be determined by the Maricopa County OET Project Manager at the time of purchase. SECTION 7: References a. Design, manufacture, test, and install per manufacturer’s requirements, the standards referenced herein, in accordance with NFPA-70 (National Electrical Code®) based on the version adopted by the authorities having jurisdiction (AHJ), IEEE C2 2007(NESC 2007), state codes, local codes, and the requirements of the AHJ. Please note that NEC® is intended to protect property and people from electrical hazards and do not necessarily address requirements for the reliable and error free operation of electrical systems. Additional requirements exceeding the safety provisions of NEC® may be required to ensure the expected performance of specific systems. ANSI/NECA/BICSI-568-2006 -- Standard for Installing Commercial Building Telecommunications Cabling ANSI/BICSI 002-2011, Data Center Design and Implementation Best Practices. ANSI/TIA-568-C.0 – Generic Telecommunications Cabling for Customer Premises ANSI/TIA-568-C.0-1-2010 – Generic Telecommunications Cabling for Customer Premises-Addendum 1, Updated References for Balanced Twisted-Pair ANSI/TIA-568-C.1-2009 – Commercial Building Telecommunications Cabling Standard ANSI/TIA-568-C.2-2009 – Balanced Twisted-Pair Telecommunications Cabling and Component Standard ANSI/TIA/EIA-568-C.3-2009 -- Optical Fiber Cabling Components Standard ANSI/TIA/EIA-569-B-2004 -- Commercial Building Standard for Telecommunications Pathways and Spaces ANSI/TIA/EIA-569-C-2005—Optical Fiber Cable Color Coding ANSI/TIA/EIA-606-A-2002 -- The Administration Standard for Commercial Telecommunications Infrastructure ANSI/J-STD-607-A -- Commercial Building Grounding and Bonding Requirements for Telecommunications ANSI-J-STD-607-B-2011 -- Commercial Building Grounding (Earthing) and Bonding Requirements for Telecommunications TIA-526-14B-2010 –OFSTP-14 Optical Power Loss Measurements of Installed Multimode Fiber Cable Plant ANSI/TIA/EIA-758-B-2011 -- Customer-Owned Outside Plant Telecommunications Infrastructure Standard ANSI/TIA/EIA-862-A–2011, Building Automation Systems Cabling Standard ANSI/TIA-942–2005, Telecommunications Infrastructure Standard for Data Centers May 17, 2012 Document 2 - Specification & Response Document Page 376 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade ANSI/TIA-1152–2009, Requirements for Field Test Instruments and Measurements for Balanced Twisted-Pair Cabling. NECA/BICSI 607-2011, Standard for Bonding and Grounding Planning and Installation Methods for Commercial Buildings TIA TSB-140 Additional Guidelines for Field Testing Length, Loss And Polarity of Optical Fiber Cabling Systems Install cabling in accordance with the most recent edition of BICSI® publications: BICSI– Telecommunications Distribution Methods Manual-12th Edition BICSI– Information Technology Systems Installation Methods Manual, 6th Edition BICSI – Installation Transport Systems Information Manual BICSI –Outside Plant Design Reference Manual-5th Edition BICSI – Wireless Design Reference Manual-3rd Edition BICSI – AV Design Reference Manual-1st Edition InfoComm International- ANSI/INFOCOMM 2M-2010, Standard Guide for Audiovisual Systems Design and Coordination Processes BICSI– Network Design Reference Manual- 7th Edition The Americans with Disabilities Act (ADA) of 1992 Title IV: Telecommunications of the Telecommunications Act, Section 4.31: Telephones of the Americans with Disabilities Act (ADA) Accessibility Guidelines (ADAAG). “Accessibility Guidelines for Buildings and Facilities”, and Section 255 NFPA 1221, Standard for the Installation, Maintenance, and Use of Emergency Services Communications Systems 2010 Edition. May 17, 2012 Document 2 - Specification & Response Document Page 377 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 10 - County Subscriber Radio Inventory May 17, 2012 Document 2 - Specification & Response Document Page 378 of 399 Maricopa County, Arizona DEPARTMENT *Consoles - Motorola Centracom Gold Elite MC Adult Probation APX6000 XTS2500 XTL2500 CONSOLES* 12030-RFP P25 Radio System Infrastructure Upgrade TOTALS 689 35 4 9 MC Animal Care APX6000 APX6500 XTS5000 XTL5000 CONSOLES* 41 47 1 3 2 MC Constables APX7000 XTS5000 1 18 MC Correct Health APX6000 33 MC County Attorney APX6000 XTL5000 10 10 MC Court Security APX6000 APX6500 XTS2500 XTL5000 CONSOLETTE 58 5 29 2 MC Emergency Mgmt APX6000 APX7500 CONSOLETTE 20 4 MC Equip Svcs APX6000 APX6500 3 13 MC Facilities APX6000 APX6500 XTS2500 3 121 20 MC Flood Control APX6000 APX6500 APX7500 5 82 1 May 17, 2012 Document 2 - Specification & Response Document Page 379 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade XTS2500 XTL2500 XTL5000 CONSOLETTE CONSOLE* 15 83 3 1 MCSO Detention APX6000 APX6500 APX7000 APX7500 XTS2500 XTL2500 APX7500 CONSOLETTE 836 66 4 1 1085 83 1 MC JUV DETENTION APX6000 240 MC Juv Probation APX6000 XTS2500 151 120 MC DOT APX6000 APX6500 APX7500 XTL2500 XTL5000 CONSOLETTE CONSOLES* 121 69 33 305 2 2 MCSO Sworn APX6000 APX7000 APX7500 APX7500 CONSOLETTE XTL2500 XTS5000 XTL5000 12 387 292 2 1 551 391 MC Medical Examiner XTS5000 XTL5000 4 1 MC Parks APX6000 APX6500 XTS2500 35 15 11 MC Protective Services APX6000 APX6500 May 17, 2012 44 5 Document 2 - Specification & Response Document Page 380 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade XTL2500 1 MC Public Health APX6000 APX6500 XTL2500 XTS2500 XTS5000 2 1 1 147 20 MC Risk Management APX6000 1 MC OET Wireless APX6000 APX6500 APX7000 APX7500 XTS5000 XTL5000 18 5 12 10 6 1 1 CONSOLES* TOTAL NUMBER OF COUNTY RADIOS 6467 LISTING OF CONTROL STATIONS ONLY No. SERIAL NUMBER IND.ID 521C HEX # 521C DEPARTMENT RADIO USER ALIAS AC DISPATCH ROOM 221 1 527CND0214 755437 D88D ANIMAL CONTROL 2 527CNF1788 755465 D8A9 ANIMAL CONTROL (BASE) 3 527CNF1789 755466 D8AA ANIMAL CONTROL (BASE) 755465 MESA OFFICE (room 226) 4 527CNF1790 755467 D8AB ANIMAL CONTROL (BASE) 755467 5 527CNF1791 755468 D8AC ANIMAL CONTROL (BASE) 6 527CNF1792 755469 D8AD ANIMAL CONTROL (BASE) 755468 AC DISPATCH 7 276CMX0144 755421 D87D COURT SECURITY NEW COURT TOWER 8 276CMX0145 755422 D87E COURT SECURITY NEW COURT TOWER 9 722AAU1554 730093 758D COURT SECURITY 730093 10 722AAU1555 730094 758E COURT SECURITY 730094 11 722AAY1884 730096 7590 COURT SECURITY 730096 12 761CMV0020 755417 D879 EMERGENCY MANAGEMENT 755417 13 761CMV0021 755418 D87A EMERGENCY MANAGEMENT 755418 14 761CMV0022 755419 D87B EMERGENCY MANAGEMENT 755419 15 761CMV0023 755420 D87C EMERGENCY MANAGEMENT 755420 16 407AWJ0079 730003 7533 EQUIPMENT SERVICES 730003 May 17, 2012 Document 2 - Specification & Response Document Page 381 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade 17 722AYS0476 730070 7576 FACILITIES MANAGEMENT 730070 18 722AYS0477 730071 7577 FACILITIES MANAGEMENT 730071 19 722AYS0478 730072 7578 FACILITIES MANAGEMENT 730072 20 276CHP0225 755026 D6F2 FLOOD CONTROL 755026 21 276CHP0226 755027 D6F3 FLOOD CONTROL 755027 22 276CJM0014 755039 D6FF FLOOD CONTROL 755039 23 407AWC0167 730037 7555 FLOOD CONTROL 730037 24 407AWC0170 730036 7554 FLOOD CONTROL 730036 25 407AWC0171 730038 7556 FLOOD CONTROL 730038 26 407AWL0080 730006 7536 FLOOD CONTROL - Backup Base 730006 27 518AWU0041 730011 753B FLOOD CONTROL - EM MGT. 730011 28 270AVU0222 730015 753F FLOOD CONTROL - NORTH YARD 730015 29 407AWL0099 730007 7537 FLOOD CONTROL- East Mesa 730007 30 761AYU0059 742951 A7C7 JAILS 742951 31 722AAC1985 742996 A7F4 JAILS - COURT SVCS. BASE 32 514CGM0331 740486 9E26 JAILS - WARD 41 BASE 33 514CHF0815 756384 DC40 JAILS BASE 756384 34 514CHF0821 756390 DC46 JAILS BASE 756390 35 514CHF0828 756397 DC4D JAILS BASE 756397 36 514CHF0829 756398 DC4E JAILS BASE 756398 37 514CHF0816 756385 DC41 JAILS BASE - 4TH AVE CONTROL 756385 38 514CHF0824 756393 DC49 JAILS BASE - 4TH AVE CONTROL 756393 39 514CHF0823 756392 DC48 756392 40 514CHF0820 756389 DC45 41 514CHF0817 756386 DC42 42 514CHF0818 756387 DC43 JAILS BASE - 4TH AVE INTAKE JAILS BASE - DURANGO CONTROL JAILS BASE - ESTRELLA CONTROL JAILS BASE - ESTRELLA O CONTROL 43 514CHF0825 756394 DC4A JAILS BASE - LBJ CONTROL 756394 44 514CHF0826 756395 DC4B JAILS BASE - LBJ INTAKE 756395 45 514CHF0827 756396 DC4C JAILS BASE - MADISON CONTROL 756396 46 514CHF0822 756391 DC47 JAILS BASE - NEW COURT TOWER RM LL1182 47 514CHF0819 756388 DC44 JAILS BASE - TOWERS CONTROL 48 518AYE0031 730059 756B MCDOT NW YARD 49 518AYE0032 730060 756C MCDOT NW YARD 50 407AWC0126 730020 7544 51 407AWC0245 730026 754A MCDOT - Bill Fugate - SE Corner MCDOT - BOBBY JACKSON'S OFFICE SW-YD 742996 WARD 41 756389 756386 756387 756388 730020 730026 52 407AWC0278 720210 4EF2 MCDOT - BUCKEYE YARD CONFERENCE ROOM 53 407AWC0458 720380 4F9C MCDOT - Buckeye Yard-Mary Coons Office BKY-YD 54 407AWC0158 730029 754D MCDOT - DAN CLEMENTS' OFFICE 730029 55 407AWC0174 720107 4E8B MCDOT - OPERATIONS 720107 56 656CMK2794 755413 D875 MCDOT - REACT 755413 57 407AWC0343 720275 4F33 MCDOT - Scott Johnson's Office 720275 58 407AWC0117 720050 4E52 MCDOT - SOUTH OPS - DOREEN'S DESK 720050 730023 730022 59 407AWC0225 730023 7547 MCDOT - SOUTH OPS - MARAILA'S DESK 60 407AWC0222 730022 7546 MCDOT - Traffic Management May 17, 2012 Document 2 - Specification & Response Document Page 382 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Center 61 407AWC0266 720198 4EE6 62 407AWC0184 730076 757C MCDOT - Traffic Management Center MCDOT-Buckeye Yard Joe Anzar Ofc 63 407AWC0453 730039 7557 MCDOT-JOHN COUNTS OFC. 730039 64 494AAU1057 744485 ADC5 MCDOT-OPS BASE STATION 744485 65 494AAU1058 744486 ADC6 MCDOT-OPS BASE STATION 744486 66 407AWC0339 720271 4F2F MCDOT-TMC 720271 67 407AWC0334 720266 4F2A MCDOT-WAREHOUSE BASE? 68 500CHV0505 746255 B4AF MCSO-SHERIFF 720266 SHERIFF JOE 69 494AAN0398 743999 ABDF MCSO-SHERIFF - APACHE LAKE SUB STATION APACHE LAKE 70 494AAJ1798 744413 AD7D MCSO-SHERIFF (BASE) 744413 71 500CHV0433 746183 B467 MCSO-SHERIFF (BASE) 746183 72 500CHV0445 746195 B473 MCSO-SHERIFF (BASE) 746195 MCSO-SHERIFF (BASE) - Avondale Substation - Squad Room 746182 720198 730076 73 500CHV0432 746182 B466 74 500CHV0434 746184 B468 75 500CHV0436 746186 B46A MCSO-SHERIFF (BASE) - Avondale Substation - Supervisor's office MCSO-SHERIFF (BASE) - Bell & Dysart B5A2 MCSO-SHERIFF (BASE) - Buckeye Shooting Range 746498 746216 76 500CJB1786 746498 746184 746186 77 500CHV0466 746216 B488 MCSO-SHERIFF (BASE) - Canyon Lake Aid Station 78 500CHV0438 746188 B46C MCSO-SHERIFF (BASE) - Cave Creek Briefing Room 746188 79 500CHV0440 746190 B46E MCSO-SHERIFF (BASE) - Dispatch 746190 80 500CHV0429 746179 B463 MCSO-SHERIFF (BASE) - District 1 Mesa 746179 81 500CHV0442 746192 B470 MCSO-SHERIFF (BASE) - EM MGT. (CIVIL DEFENSE) 746192 B46D MCSO-SHERIFF (BASE) - Fountain Hills Briefing Room 746189 82 500CHV0439 746189 83 500CHV0435 746185 B469 84 500CHV0430 746180 B464 MCSO-SHERIFF (BASE) - Litchfield Town Hall 214 W. Wig Wam Blvd. MCSO-SHERIFF (BASE) - Queen Creek 85 500CHV0441 746191 B46F MCSO-SHERIFF (BASE) - Saguaro Lake Aid Station 746191 B465 MCSO-SHERIFF (BASE) - Sun Lakes Posse Building 746181 MCSO-SHERIFF (BASE) - Training Center 746193 86 500CHV0431 746181 87 500CHV0443 746193 B471 88 500CHV0444 746194 B472 89 500CHV0437 746187 B46B 90 494AAJ1801 744416 AD80 91 494AAJ1817 744432 AD90 92 494AAJ1792 744407 93 494AAJ1786 744401 94 494AAJ1803 744418 May 17, 2012 MCSO-SHERIFF (BASE) - Training Center MCSO-SHERIFF (BASE) Wickenburg 746185 746180 746194 746187 744416 AD77 MCSO-SHERIFF (BASE)-Aviation MCSO-SHERIFF (BASE)-Avondale Jail MCSO-SHERIFF (BASE)-Bartlett Lake AD71 MCSO-SHERIFF (BASE)-Blue Point 744401 AD82 MCSO-SHERIFF (BASE)-Blue Point 744418 744432 744407 Document 2 - Specification & Response Document Page 383 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade 95 494AAJ1807 744422 AD86 MCSO-SHERIFF (BASE)-Blue Point 744422 96 494AAJ1787 744402 AD72 MCSO-SHERIFF (BASE)-BOB 744402 AD74 MCSO-SHERIFF (BASE)-Canyon Lake Aid Station 744404 97 494AAJ1789 744404 98 494AAJ1818 744433 AD91 MCSO-SHERIFF (BASE)-DISPATCH 744433 99 494AAJ1795 744410 AD7A MCSO-SHERIFF (BASE)-Gila Bend 744410 AD7C MCSO-SHERIFF (BASE)-Glendale Aviation Hanger 744412 744406 744423 100 494AAJ1797 744412 101 494AAJ1791 744406 AD76 MCSO-SHERIFF (BASE)-Intelligence Lt. Whitney 102 494AAJ1808 744423 AD87 MCSO-SHERIFF (BASE)-K-9 103 494AAJ1810 744425 AD89 104 494AAJ1815 744430 AD8E MCSO-SHERIFF (BASE)-Lake Pleasant MCSO-SHERIFF (BASE)-Lake Pleasant 105 494AAJ1793 744408 AD78 MCSO-SHERIFF (BASE)-Propery & Evidence Room 744408 106 494AAJ1788 744403 AD73 MCSO-SHERIFF (BASE)-SEC Jail 744403 107 500CHK0236 755023 D6EF MEDICAL EXAMINER - FORENSIC SCIENCE CENTER 744425 744430 ME OFFICE 108 722AZL0517 730083 7583 109 722AZL0511 730077 757D PARKS AND RECREATION - LP Operations Center PARKS AND RECREATION- CC contact 110 722AZL0513 730079 757F PARKS AND RECREATION- LP DOC office 111 722AZL0519 730085 7585 112 722AZL0510 730069 7575 113 722AZL0516 730082 7582 114 722AZL0514 730080 7580 115 722AZL0512 730078 757E 116 722AZL0518 730084 7584 117 722AZL0520 730086 7586 PARKS AND RECREATION- LP hotsprin PARKS AND RECREATION- LP maint PARKS AND RECREATIONMcDowell PARKS AND RECREATION- Usery off PARKS AND RECREATION- White tank PARKS AND RECREATION-CC office PARKS AND RECREATION-Est office 118 722AZL0472 730081 7581 PARKS AND RECREATION-LK PLE CONTACT STATION 730081 119 722ABS1674 720777 5129 PROTECTIVE SERVICES 11200 120 722ABS1675 720778 512A PROTECTIVE SERVICES 11570 121 722ABS1676 720779 512B PROTECTIVE SERVICES 111005 122 722AYS0475 730066 7572 PROTECTIVE SERVICES 730066 123 722CFM0722 730025 7549 PROTECTIVE SERVICES DURANGO GARAGE 730025 124 722CDE1427 730104 7598 PUBLIC HEALTH - BIO DEFENSE 730104 125 527CNB0109 752940 CECC WIRELESS SYSTEMS 752940 730083 730077 730079 730085 730069 730082 730080 730078 730084 730086 126 527CMX0675 752937 CEC9 WIRELESS SYSTEMS RADIO SHOP GARAGE 127 527CMX0676 752938 CECA WIRELESS SYSTEMS 752938 128 527CMX0677 752939 CECB WIRELESS SYSTEMS 752939 129 656CMX0830 752933 CEC5 WIRELESS SYSTEMS 752933 130 656CMX0831 752934 CEC6 WIRELESS SYSTEMS ZONE ROOM May 17, 2012 Document 2 - Specification & Response Document Page 384 of 399 Maricopa County, Arizona 131 656CMX0832 May 17, 2012 752935 12030-RFP P25 Radio System Infrastructure Upgrade CEC7 WIRELESS SYSTEMS BENCH RADIO Document 2 - Specification & Response Document Page 385 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 11 - Non-County Subscriber Radio Inventory May 17, 2012 Document 2 - Specification & Response Document Page 386 of 399 Maricopa County, Arizona Agency 12030-RFP P25 Radio System Infrastructure Upgrade Qty. AZ Dept. of EM Mgt. XTS5000 3 AZ Dept. of EM Mgt. XTS5000 3 Avondale Public Works XTS2500 XTL2500 XTL5000 9 45 1 Central Arizona Project XTS5000 2 Carefree Marshall XTS2500 1 Cave Creek Marshall XTS2500 XTS3000 Astro Spectra XTL5000 XTL5000 Consolette XTS5000 1 2 2 2 1 1 Dept. of Public Safety Astro Spectra XTS5000 1 23 DOJ Cache XTS2500 XTS5000 APX7000 82 310 3 Fort McDowell Astro Spectra 1 Fountain Hills Fire Dept. XTS5000 7 Fountain Hills Posse XTS3000 XTS5000 5 4 Gilbert PD XTL5000 Consolette 1 May 17, 2012 Document 2 - Specification & Response Document Page 387 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade GITA XTS2500 2 Glendale PD XTL5000 6 KPNX Astro Spectra 1 Mesa PD XTL5000 Consolette XTS5000 1 15 Motorola MTS2000 XTS3000 XTS5000 APX7000 APX7500 3 1 3 1 1 Palo Verde Spectra 1 Paradise Valley MCS2000 MTS2000 XTL5000 XTL5000 Consolette XTS5000 23 2 3 6 34 Privately Owned Posse MTS2000 MTX8000 XTS2500 XTS3000 Astro Spectra XTL5000 XTS5000 APX 7000 1 2 36 61 15 20 90 1 Rural Metro APX7000 APX75000 7 5 Sun City Posse Astro Spectra XTS3000 1 8 May 17, 2012 Document 2 - Specification & Response Document Page 388 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Sun City West Posse Astro Spectra LTS2000 LCS2000 XTS3000 2 40 18 5 Surprise Public Works Astro Spectra Consolette MTS2000 1 59 Union Pacific Railroad XTS5000 1 TOTAL NON-COUNTY RADIOS 986 May 17, 2012 Document 2 - Specification & Response Document Page 389 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 12 - Definition of Acronyms Used in This Document May 17, 2012 Document 2 - Specification & Response Document Page 390 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade A AC ADEQ AES AGC AGL AIRS ALI AMSL ANI ANSI APCO ASCE ASCII ASET ASR ASU AWG AZDPS AzWIN BLM BOCA BPS C&C CAD Ampere Alternating Current Arizona Department of Environmental Quality Advanced Encryption Standard Automatic Gain Control Above Ground Level Arizona Interagency Radio System Automatic Location Identification Above Mean Sea Level Automatic Number Identification American National Standards Institute Association of Public Safety Communications Officers American Society of Civil Engineers American Standard Code for Information Interchange Arizona Strategic Enterprise Technology Antenna Structure Registration Arizona State University American Wire Gauge Arizona Department of Public Safety Arizona Wireless Integrated Network United States Bureau of Land Management Building Officials and Code Administrators Bits per Second Command and Control Computer-Aided Dispatch (public safety computer system), or ComputerAided-Drawing (computer system for producing construction and architectural drawings) CCE CO CODEC Console Central Electronics Central Office (telephone switching center) EnCoder-Decoder (typically used for digital audio and video) Control Station Fixed radio operating on mobile frequencies; typically a desktop radio but often a mobile radio permanently mounted in a fixed location Counterpoise A network or radial system of wires below grade used to couple lightning energy to ground CPS CPU CRT CTCSS DAQ dB dBc dBm Characters per Second Central Processing Unit Cathode Ray Tube (video display device) Continuous Tone Coded Squelch Systems Delivered Audio Quality, as defined in TSB-88 Decibel Decibels referenced to carrier power level Decibels referenced to one milliWatt. May 17, 2012 Document 2 - Specification & Response Document Page 391 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Desktop Remote Control Unit Small Dispatcher console setting on desktop; Not a full dispatch console DMS DPS DS-0 Data Management System Department of Public Safety 56 kilobit or 64 kilobit per second (one digital voice channel) data stream per telephone company specifications DS-1 1.544 kilobit per second data stream (24 multiplexed digital voice channels) per telephone company specifications DS-3 44.736 kilobit per second data stream (28 multiplexed DS-1 data streams) per telephone company specifications DTMF E-9-1-1 EIA EMI EMT EOC ERP ESD F FAA FCC FD FDMA FEMA Fixed Equipment Dual-Tone Multi-Frequency (touch-tone) Enhanced 9-1-1 Electronics Industry Association Electromagnetic Interference Electrical Metallic Tubing or Emergency Medical Technician Emergency Operations Center Effective Radiated Power Electro-Static Discharge Fahrenheit Federal Aviation Administration Federal Communication Commission Fire Department Frequency Division Multiple Access Federal Emergency Management Agency Radio towers and antenna systems, equipment shelters, repeaters, base stations, consoles, controllers, microwave, etc. Fiscal Year Gigahertz State of Arizona Government Information Technology Agency Ground Fault Circuit Interrupter Geo-Positioning Satellite, Global Positioning Satellite Portable Radio High Stability Master Oscillator Heating, Ventilating, and Air Conditioning Hertz Input/Output International Building Code Identifier, identification of a specific radio unit Identification Inter-Governmental Agreement Communications with units/agencies on differing radio systems Internet Protocol Inter-Sub-System Interface FY GHz GITA GFCI GPS Handheld Radio HSMO HVAC Hz I/O IBC ID ID IGA Interoperability IP ISSI May 17, 2012 Document 2 - Specification & Response Document Page 392 of 399 Maricopa County, Arizona kbps kHz KMF KVL LAN LCD LED LPI MAC MCSO MDC MDM MDT MHz Mobile Radio MODEM MOU MPH MPLS MTBF MUX NEC NEMA NENA NFPA NFPA 70 NPSPAC NTP OET OSHA OTAP OTAR P-P P25 P25 CAI P25 Standards PA PABX PCWIN PD PMI PMO May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade kilobits per second kiloHertz Key Management Facility Key Variable Loader Local Area Network Liquid Crystal Display Light Emitting Diode Lightning Protection Institute, Harvard, IL Media Access Control Maricopa County Sheriff's Office Mobile Data Computer Mobile Data Modem Mobile Data Terminal Megahertz Two-way radio designed to be permanently installed in/on an automobile, truck, van, motorcycle, ATV or boat Modulator/Demodulator, used to link computer equipment Memorandum of Understanding Miles per hour Multi-Protocol Label Switching Mean Time Between Failures Audio or data multiplexer National Electrical Code National Electrical Manufacturer’s Association National Emergency Number Association National Fire Protection Association NFPA Standard No. 70; the National Electrical Code National Public Safety Planning Advisory Committee Notice To Proceed Maricopa County Office of Enterprise Technology Occupational Safety and Health Administration Over the Air Programming Over the Air Rekeying Peak-to-Peak APCO Project 25 APCO Project 25 Common Air Interface The TIA-102 suite of standards for APCO Project 25 radio equipment Public Address Private Automatic Branch Exchange Pima County Wireless Interoperable Network Police Department Project Management Institute, Newtown Square, PA Project Management Office Document 2 - Specification & Response Document Page 393 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Portable Radio PS PSAP PSIC PTT PTT ID RAID RCV, RCVR, RX RF RFI RFP RMS A two-way radio designed for portable (primarily handheld) operation Public Safety Public Safety Answering Point Public Safety Interoperable Communications Push to Talk Unique identification number of a radio transmitted during PTT Redundant Array of Independent Disks Receive, Receiver Radio Frequency Radio Frequency Interference Request For Proposals Records Management System (computer system), or Root-Mean-Square (method of measuring alternating current voltages) RPM RWC SWBCG System Access Time Revolutions Per Minute Regional Wireless Cooperative Southwest Border Communications Group The time interval between PTT and assignment of a radio channel allowing a conversation to begin. Radio communications originating with the field user and received by a base station. Radio communications originating at the base station and received by a field user. Transmission Control Protocol Time Division Multiplex Time Division Multiple Access Telecommunications Industry Association Trunked OPen AriZona - Mesa area radio system TRWC TOPAZ Regional Wireless Cooperative TIA/EIA Telecommunications Systems Bulletin TSB88-(latest revision), "Wireless Communications Systems - Performance In Noise and InterferenceLimited Situations - Recommended Methods For Technology-Independent Modeling, Simulation, and Verification” Talk-In Talk-Out TCP TDM TDMA TIA TOPAZ TRWC TSB-88 TX UASI UDP UPS USB USFS UV VAC VDC VSWR W May 17, 2012 Transmit Urban Area Security Initiative User Datagram Protocol Uninterruptible Power Supply Universal Serial Bus United States Forest Service Ultraviolet Volts Alternating Current Volts Direct Current Voltage Standing Wave Ratio Watts Document 2 - Specification & Response Document Page 394 of 399 Maricopa County, Arizona WAN WBS XMIT XMTR YRCS May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Wide Area Network Work Breakdown Structure Transmit Transmitter Yuma Regional Communication System Document 2 - Specification & Response Document Page 395 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 13 - Map of County-Owned Parcels May 17, 2012 Document 2 - Specification & Response Document Page 396 of 399 Maricopa County, Arizona May 17, 2012 12030-RFP P25 Radio System Infrastructure Upgrade Document 2 - Specification & Response Document Page 397 of 399 Maricopa County, Arizona 12030-RFP P25 Radio System Infrastructure Upgrade Appendix 14 – Existing TDM Circuits for Telephone and Data May 17, 2012 Document 2 - Specification & Response Document Page 398 of 399 Maricopa County, Arizona T-1# 12030-RFP P25 Radio System Infrastructure Upgrade Origin Site Destination Site Channel Bank Purpose 1 CCB Voter Room Gila Bend Channel Bank GLB1 MCSO Substation Phone & Data 4 CCB Voter Room Wickenburg Channel Bank WKB1 Wickenburg Sub Phone & Data 6 CCB Voter Room Lake Pleasant T1 to Sheriff MCSO Sub Phone & Data 7 CCB Voter Room Lake Pleasant Channel Bank LPT1 LKP Parks Phone & Data 9 CCB Voter Room Bell / Dysart Channel Bank BEL1 MCSO Sub Phone & Data 10 CCB Voter Room Avondale Channel Bank AVD1 MCSO Sub Phone & Data 29 Durango Wickenburg Test Circuit Wickenburg Sub 37 Durango Lake Pleasant Channel Bank LKP Parks Phone & Data 53 CCB Voter Room Bronco Butte Apache Lake MCSO Sub Phone & Data 54 CCB Voter Room Wickenburg T1 to Sheriff MCSO Sub Phone & Data 55 CCB Voter Room Wickenburg T1 to Sheriff MCSO Sub Phone & Data 56 CCB Voter Room White Tanks East City of Phoenix WTE Lower bldg 63 CCB Voter Room Desert Outdoor Center T1 to Parks LKP Outdoor Center Phone & Data 70 Thompson Peak Central Courts Phoenix Transit 71 Thompson Peak White Tanks East Phoenix Transit 72 Gillen Central Courts Phoenix Transit 73 Gillen Central Courts Phoenix Transit Lower Bldg WTE In addition to the above, there is one DS-0 circuit that runs between the Emergency Management site and the White Tanks West site that is carried via the “Overhead” capacity of the OC-3 microwave loop and is not part of the T-1 circuits listed in the above table. May 17, 2012 Document 2 - Specification & Response Document Page 399 of 399

Specification & Response Document

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib