Advertisement
wachiorsino

Infrastructure Sub-System - Naval

Oct 19th, 2012
126
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 47.29 KB | None | 0 0
  1.  
  2. A B C D E F G H
  3. 1 ATTACHMENT 001 GENERAL REQUIREMENTS - CROSS REFERENCE MATRIX
  4. 2 GENERAL REQUIREMENTS Proposal Location
  5. 3 All equipment shall be APCO Project 25 (P25) Phase 1 Standards compliant and upgradeable (via software only) to 6.25 kHz effective bandwidth
  6. 4 The proposed system shall not allow two (2) co-channel transmitters to operate simultaneously unless in optimized simulcast mode.
  7. 5 All network switches and routers shall be CISCO.
  8. 6 All equipment shall be housed in lockable 19” EIA standard racks with 48 rack unit (RU) of usable space. The rack enclosure will have a fan, mounted to promote air flow.
  9. 7 All software programs, software and hardware configurations, and any other settings in the LMR system shall be recorded and backed up daily.
  10. 8 All LMR transmit equipment shall utilize Passive Intermodulation Distortion (PIM) mitigating connectors and components.
  11. 9 The system shall meet the following:
  12. Channel Number Transmit Receive
  13. 1 169.5750 162.2500
  14. 2 169.8375 162.6125
  15. 3 170.1375 162.8000
  16. 4 170.3750 163.1625
  17. 5 170.5750 163.6000
  18. 6 171.0000 164.0125
  19. 7 171.4125 164.3250
  20. 8 171.7875 164.6125
  21. 9 172.3875 164.8125
  22. 10 172.6875 165.0375
  23. 11 172.9625 165.5375
  24. 12 173.1625 165.7750
  25. 13 173.4750 166.2250
  26. 14 173.8125 166.4250
  27. 10 All subscribers (mobile, portables, control stations) shall operate within 136 MHz to 174 MHz.
  28. 11 All base stations and repeaters shall operate within 150 MHz to 174 MHz.
  29. 12 Power
  30. 13 All equipment shall operate on 120 Volts AC at 60 Hz unless otherwise specified.
  31. 14 Environment
  32. 15 The temperature operating range of all equipment shall be from -22 Degrees Fahrenheit to 140 Degrees Fahrenheit.
  33. 16 The operating humidity of all equipment shall be in the range of 20% to 80% relative humidity, non-condensing.
  34. 17 Voice Encryption and Over-the-Air Rekeying (OTAR) Proposal Location
  35. 18 The proposed trunked system shall be able to support voice encryption on all the RF channels within the system.
  36. 19 The proposed system shall support FIPS 140-2 Level 2 or higher Certified, Type III encryption (AES 256 bit).
  37. 20 The proposed system shall provide keyloaders.
  38. 21 Voice encryption shall be capable of generating AES (256-bit) encryption keys and transmitting those keys to identified subscribers and talkgroups through OTAR. Any radios not rekeyed shall be identified, buffered and shall be rekeyed when the subscriber unit reenters the coverage area.
  39. 22 OTAR shall be able to zeroize any compromised subscriber radio rendering it incapable of use.
  40. 23 The proposed system shall include a key management system.
  41. 24 Over the Air Programming (OTAP)
  42. 25 The proposed system shall have OTAP capabilities to enable making software changes to mobile and portable subscriber units. This feature applies to both trunking and conventional systems.
  43. 26 The system administrator shall be able to provide the capability to prioritize OTAP relative to voice and data communications with the exception of an emergency call, which shall always be given a higher priority. Subscribers shall continue to operate normally during the OTAP process.
  44. 27 OTAP shall not change the subscribers encryption key.
  45. 28 System Alarm
  46. 29 The proposed LMR system shall include an alarm system dedicated to the trunked system that has external input capabilities that capture transducer contact closure (digital) and 4 to 20 ma loop current (analog).
  47. 30 Alarm status information shall be accessible from the system manager workstation. The system supervisor shall be able to receive alarm conditions concerning all major components of the LMR system to include base station repeaters and controllers.
  48. 31 The proposed system shall have the ability to print a hardcopy of reports, file records and event reconstruction, as they occur. A network printer shall be included with the system manager workstation.
  49. 32
  50. 33 At a minimum, the following system alarms must be reported to the system manager workstation:
  51. 34 • Radio Equipment
  52. 35 • Low Transmitter power
  53. 36 • High Transmitter reflected power / High Voltage Standing Wave Ratio (VSWR)
  54. 37 • Unidentified carrier on unassigned voice channel
  55. 38 • Signaling interface failure between base and controller
  56. 39 • Audio circuit failure between base and controller
  57. 40 • Voting receiver failed
  58. 41 • Voting receiver disabled
  59. 42 • Station major alarm
  60. 43 • Station minor alarm
  61. 44 • Controller major alarm
  62. 45 • Controller minor alarm
  63. 46 • GPS receiver alarm
  64. 47 • Dispatch Center Alarms
  65. 48 • Logging Recorder Full
  66. 49 • Logging Recorder Alarm
  67. 50 • Master Time Source Loss of Sync
  68. 51 • Console Electronics Power Supply Failure
  69. 52 • Console Electronics Major Alarm
  70. 53 • Console Electronics Minor Alarm
  71. 54 • Control/signaling channel data integrity (high speed data)
  72. 55 • Low speed data integrity
  73. 56 • Failure of trunking operation of each channel
  74. 57 • System interference reception
  75. 58 • High temperature alarm
  76. 59 • High humidity alarm
  77. 60 The alarm system shall provide text messages, paging, and e-mail alerts to designated system managers and technicians. These messages shall provide alarm notifications in common language format.
  78. 61 The alarm system shall support password protected remote login by system managers and technicians to review system status.
  79. 62 Activity Reports Proposal Location
  80. 63 The activity reports shall be available in both summary and detail report format. Reports must be able to be generated over a user defined time period. Report formats shall be compatible with Microsoft Office 2007.
  81. 64 The activity report data shall have enough storage to contain a minimum of 3 years of radio system activity.
  82. 65
  83. 66 The activity report data shall, at a minimum, be stored and able to be searched by the following fields in appropriate combinations in both default reports and user customized reports:
  84. 67 • Date
  85. 68 • Time
  86. 69 • PTT Number
  87. 70 • Average PTT number over time
  88. 71 • Average PTT duration over time
  89. 72 • System
  90. 73 • Zone
  91. 74 • Site ID
  92. 75 • Site Alias
  93. 76 • Site Use
  94. 77 • Site Summary
  95. 78 • Site Utilization
  96. 79 • Site GoS
  97. 80 • Site Statistical GoS
  98. 81 • Air Time in Seconds
  99. 82 • Air Time in Minutes
  100. 83 • Call Type
  101. 84 • Group Call
  102. 85 • Dispatch Call
  103. 86 • Private Call
  104. 87 • Telephone Interconnect Call
  105. 88 • Data Call
  106. 89 • Emergency Call
  107. 90 • Initiating Radio ID
  108. 91 • Initiating Radio Alias
  109. 92 • Target Radio ID
  110. 93 • Target Radio Alias
  111. 94 • Busy Duration in Seconds
  112. 95 • Busy Start Time
  113. 96 • Busy Reason
  114. 97 • Busy Site
  115. 98 • Private Call Contention
  116. 99 • Resource not Available in Seconds
  117. 100 • Partial Busy in Seconds
  118. 101 • Channel Assignment
  119. 102 • Talkgroup ID
  120. 103 • Talkgroup Alias
  121. 104 • Talkgroup Usage
  122. 105 • Event
  123. 106 • Event Message
  124. 107 • Event Description
  125. 108 • Reject Reason
  126. 109 • Affiliations
  127. 110 • Failed Calls
  128. 111
  129. 112
  130. 113
  131. 114
  132. 115
  133. 116
  134. 117
  135. 118
  136. 119
  137. 120
  138. 121
  139. 122
  140. 123
  141. 124
  142. 125
  143. 126
  144. 127
  145. 128
  146. 129
  147. 130
  148. 131
  149. 132
  150. 133
  151. 134
  152. 135
  153. 136
  154. 137
  155. 138
  156. 139
  157. 140
  158. 141
  159. 142
  160. 143
  161. 144
  162. 145
  163. 146
  164. 147
  165. 148
  166. 149
  167. 150
  168. 151
  169. 152
  170. 153
  171. 154
  172. 155
  173. 156
  174. 157
  175. 158
  176. 159
  177. 160
  178. 161
  179. 162
  180. 163
  181. 164
  182. 165
  183. 166
  184. 167
  185. 168
  186. 169
  187. 170
  188. 171
  189. 172
  190. 173
  191. 174
  192. 175
  193. 176
  194. 177
  195. 178
  196. 179
  197. 180
  198. 181
  199. 182
  200. 183
  201. 184
  202. 185
  203. 186
  204. 187
  205. 188
  206. 189
  207. 190
  208. 191
  209. 192
  210. 193
  211. 194
  212. 195
  213. 196
  214. 197
  215. 198
  216. 199
  217. 200
  218. 201
  219. 202
  220. 203
  221. 204
  222. 205
  223. 206
  224. 207
  225. 208
  226. 209
  227. 210
  228. 211
  229. 212
  230. 213
  231. 214
  232. 215
  233. 216
  234. 217
  235. 218
  236. 219
  237. 220
  238. 221
  239. 222
  240. 223
  241. 224
  242. 225
  243. 226
  244. 227
  245. 228
  246. 229
  247. 230
  248. 231
  249. 232
  250. 233
  251. 234
  252. 235
  253. 236
  254. 237
  255. 238
  256. 239
  257. 240
  258. 241
  259. 242
  260. 243
  261. 244
  262. 245
  263. 246
  264. 247
  265. 248
  266. 249
  267. 250
  268. 251
  269. 252
  270. 253
  271. 254
  272. 255
  273. 256
  274. 257
  275. 258
  276. 259
  277. 260
  278. 261
  279. 262
  280. 263
  281. 264
  282. 265
  283. 266
  284. 267
  285. 268
  286. 269
  287. 270
  288. 271
  289. 272
  290. 273
  291. 274
  292. 275
  293. 276
  294. 277
  295. 278
  296. Infrastructure Sub-System
  297.  
  298. A B C
  299. 1 ATTACHMENT 002 INFRASTRUCTURE SUB-SYSTEM - CROSS REFERENCE MATRIX
  300. 2 INFRASTRUCTURE SUB-SYSTEM Proposal Location
  301. 3 The infrastructure sub-system shall have one simulcast base transceiver located at each site (indoor and outdoor) as a status monitored powered shelf spare unit.
  302. 4 The infrastructure sub-system shall have a trunked radio system management that includes configuration management, encryption management, system traffic history, and system alarm/condition monitoring.
  303. 5 The infrastructure sub-system shall have an IP Interoperability Gateway that shall be capable of connecting outside agencies to USCP’s simulcast radio network.
  304. 6 The infrastructure subsystem shall have the capability to operate in Message or Transmission Trunking Mode.
  305. 7 Control Channel
  306. 8 Any channels in the system shall be capable of acting as the control channel.
  307. 9 The infrastructure subsytem shall automatically revert, with no negative system performance impact, to a minimum of four designated alternate control channels in the event that the active control channel becomes inoperable.
  308. 10 The trunked radio system controller shall have the capability of detecting an unauthorized signal on any of the RF channel receivers. If such a signal is detected, the system controller shall be capable of removing the associated channel transmitters and receivers from service for the duration of the interference.
  309. 11 If the interference or unauthorized signal appears on the control/signaling channel, the infrastructure subsystem shall remove the channel being interfered with from service and use another RF channel as the control channel.
  310. 12 System Access
  311. 13 After the user presses the Push to Talk (PTT) button, the infrastructure subsystem shall take less than 0.5 seconds to complete the channel assignment process.
  312. 14 Priority
  313. 15 The infrastructure subsystem shall be capable of assigning and managing a minimum of five (5) user defined levels of priority. The highest priority shall be the emergency or "panic" level.
  314. 16 Under emergency situations (ruthless preemption), the infrastructure subsystem shall allow authorized dispatchers to break through an ongoing conversation.
  315. 17 When users activate the emergency button/switch, the infrastructure subsystem shall allow users to gain immediate access to a channel and preempt all other priority levels and interrupt on-going communications if necessary.
  316. 18 The infrastructure subsystem shall have the capability to display the unit ID initiating the emergency call numerically, alpha-numerically, or alpha-only.
  317. 19 Busy Queuing Call Back
  318. 20 The infrastructure subsystem shall provide a callback feature when any unit is placed into a system busy queue. The unit requesting the channel shall be notified automatically by the LMR system when it assigns the unit a channel after the unit is placed in the queue. The infrastructure subsystem shall cause the field unit to emit an audible alert, specific for callback, and the unit shall automatically have access to the assigned channel.
  319. 21 Unit Kill/Stun
  320. 22 The infrastructure subsystem shall provide the capability to allow the system supervisor, using a system manager workstation to disable any system subscriber unit affiliated with the system. The disabling of a field unit shall prevent the unit from monitoring any voice communications on any channel or user group in the system.
  321. 23 System Management
  322. 24 The infrastructure subsystem management equipment for control of the LMR system shall be provided with an operating system that is compatible with a GUI Microsoft Windows Operating System. The system manager shall allow data entry and retrieval from the system.
  323. 25 Database
  324. 26 A database shall be provided that will store system and user profiles such as user group access, priority levels, dynamic regrouping plans, authorization codes, interconnect access, etc.
  325. 27 System Diagnostics
  326. 28 The diagnostic system shall continuously test all RF repeater stations, site controllers, and other critical hardware and software functions. Should any abnormalities be found during a test sequence, the abnormality shall be logged in plain text format (not coded characters).
  327. 29 Base Station Repeaters
  328. 30 The base station repeaters shall provide a minimum of 25 Watts/maximum of 100 Watts of RF Power Output and be adjustable throughout the range.
  329. 31 Interoperability Gateway
  330. 32 The infrastructure subsystem shall have an Interoperability Gateway IP solution at both the primary site and the mirror site. The Interoperability Gateway IP gateway equipment connection point shall operate with all connected equipment such as other LMR radios, satellite phones, cell phones, landlines phones, Dispatch Consoles, and PCs. The connections shall be set up through Dispatch Console to Dispatch console IP connections.
  331. 33 The IP gateway shall provide intercom connection capabilities between IP gateway connection point equipment.
  332. 34 The interoperability gateway equipment shall, at a minimum, address the following:
  333. 35 • Redundancy that provides protection from power supply failures,
  334. 36 • Redundancy that provides protection from chassis common equipment failures, and
  335. 37 • Redundancy that provides protection from connection point interface failures.
  336. 38 The interoperability gateway shall be configured for backhaul (WAN) route redundancy.
  337. 39 The interoperabiltiy gateway shall, at a minimum, implement either the Bridging System Interface (BSI) specification or the P25 Inter RF Sub-System Interface (ISSI) as part of the VoIP capability.
  338. 40 The interoperability Gateway shall have twenty five (25) Conventional Radio Interfaces with expandibility up to fifty (50) Conventional Radio Interfaces.
  339. 41 The Interoperability Gateway Interface minimum Requirements are as follows:
  340. - Public Telephone Switch Network (PTSN) QTY 10 Interfaces
  341. - Internet Protocol (IP) (Radio over IP, RoIP to RoIP) QTY 20 Interfaces
  342. - Radio QTY 40 Interfaces
  343. - Session Initiation Protocol (SIP) QTY 10 Interfaces
  344. 42
  345. VRS
  346.  
  347. A B C
  348. 1 ATTACHMENT 003 VRS - CROSS REFERENCE MATRIX
  349. 2 VOICE LOGGING RECORDER SUB-SYSTEM (VRS) Proposal Location
  350. 3 The VRS shall have two recorders (parallel recording): one at each dispatch center
  351. 4 The VRS shall have the ability to record: P25 IP Trunked radio, VOIP (Avaya CS2100), Analog, T1, E1, ISDN, and Digital PBX support the two (2) dispatch centers that are geographically separated.
  352. 5 The Recorder shall be capable of interfacing with the USCP 911 server and record ANI/ALU.
  353. 6 The VRS shall operate on the radio IP network and be included in the radio’s security groups, network security, and fault management systems.
  354. 7 Encrypted voice messages shall remain encrypted throughout transport to the voice recorder
  355. 8 The VRS shall not have degradation of audio quality during storage, retrieval and playback options.
  356. 9 The Recorder shall capture the following minimum items per radio call, but shall not limited to:
  357. • Date and time stamp
  358. • Call Type
  359. • Unit ID/alias
  360. • Talkgroup name
  361. • Originating Unit ID/alias
  362. • Site ID of originating call
  363. 10 The Recorder shall capture the following minimum items from the console, but shall not limited to:
  364. • Emergency Alarm/Acknowledge
  365. • Resource Status
  366. • Repeat Control
  367. • Main/Alt Status
  368. • Talk Group Priority status
  369. • Call Alert
  370. 11 The Recorder shall capture the following minimum items per telephony call, but shall not limited to:
  371. • Channel Name
  372. • Time/Date
  373. • Call Duration
  374. • Dialed Number
  375. • Caller ID Number
  376. 12 The Recorder shall have the following minimum playback and monitor features, but shall not limited to:
  377. • Simultaneous record/play
  378. • Live Monitor
  379. • Local Speaker
  380. • Remote PC
  381. • Continuous
  382. • Looped
  383. • Variable Speed
  384. • Fast Forward
  385. • Rewind
  386. 13 Remote Access Software shall be a fully-featured Windows desktop client with the ability to search on all captured fields, individually, or in combinations.
  387. 14 Remote Access Software shall have “Instant Recall” for console operator to immediately playback position audio for recent calls for no less than 30min.
  388. 15 User interface playback client must allow network manager the ability to assign specific playback options and channels to individual users.
  389. 16
  390. 17 The VRS Recorder shall support:
  391. • Multiple compression rates, and vocoder formats
  392. • Simultaneous recording of telephony/radio channels
  393. • > 20 VoIP telephony (up to 3 independent VoIP systems)/per dispatch site
  394. • > 10 analog/digital telephony/per dispatch site
  395. • > 13 trunked radio channels
  396. • > 20 conventional radio channels
  397. 18 All Recording software must be certified/approved with trunking vendor
  398. 19 The data storage capacity requirement will be minimum of 3 Terabytes (TB)
  399. 20 The VRS shall meet the following minimum Recorder Performance requirements:
  400. 21 Analog Inputs:
  401. 22 • Balanced and isolated inputs
  402. 23 • Telephony input impedance 10M Ω
  403. 24 • Signal to noise ratio >30db
  404. 25 • Crosstalk coupling ≥-60db
  405. 26 • Analog recording inputs 600Ω
  406. 27 • Dynamic range >-40dbm
  407. 28 • Frequency response >300-3400hz
  408. 29 Triggers (configurable per channel):
  409. 30 • Level or energy detection, manually adjustable
  410. 31 • External contact closure
  411. 32 • On/Off hook detection
  412. 33 • Continuous recording
  413. 34
  414. Dispatch Console Sub-System
  415.  
  416. A B C
  417. 1 ATTACHMENT 004 - DISPATCH CONSOLE SUB-SYSTEM - CROSS REFERENCE MATRIX
  418. 2 DISPATCH CONSOLE SUB-SYSTEM Proposal Location
  419. 3 The radio consoles at each dispatch center must have the ability to be manned and operated simultaneously.
  420. 4 Consoles shall have the capability to patch encrypted channels and encrypted talkgroups simultaneously.
  421. 5 Consoles shall have the capability to send a one-way broadcast to all units. This capability shall not utilize more than 1 (one) radio system channel to send to all units on air.
  422. 6 Consoles shall have the capability to send a one-way broadcast to multiple talkgroups at once and receive traffic from each of those same talkgroups independently.
  423. 7 Field units and radio consoles shall be capable of transmitting, a minimum of three (3) 'clear' and encrypted messages and notifying the users by means of distinctively different audible tones. These tones shall be programmable.
  424. 8 The radio console shall be Internet Protocol (IP) based and be fully modular and built with functionalities and reliability expected in the public safety sector to support a minimum of 25 radio dispatcher positions (15 located at the primary site, 10 at the mirror site).
  425. 9 The console subsystem shall be capable of supporting conventional and trunked radio operations as well as phone line operations.
  426. 10 The console subsystem shall have two (2) dual headset jacks that provide “side tone” into the users ear while utilizing PTT. These jacks shall be compatible with either four (4) or six (6) wire headsets. Inserting the headset plug into the headset jack shall automatically disconnect the console microphone and select audio speaker. The dual jacks shall be configured as one in the operator mode and the other in the monitor mode with control preemption.
  427. 11 The consoles shall have four (4) headsets that can operate with the headset jacks and have a mid-cord plug/jack for each console position.
  428. 12 The base station transmitters shall be keyed via the monitor display, channel control module "transmit" switch, footswitch with 25' cable, or by the transmit switch that is part of the headset. All dispatch consoles must have the ability to cross mute co-located consoles.
  429. 13 All consoles shall have the ability to receive Emergency Alarms on programmed talkgroups. Any position shall be able to acknowledge the audible alarm to silence it on ALL consoles. All consoles shall have the ability to clear the emergency from the system if authorized.
  430. 14 The console shall have a programmable subscriber emergency activation that shall be routed to dispatcher consoles regardless of the talkgroup, selected by the subscriber unit.
  431. 15 Dispatch consoles shall not have the ability to remove any sound files from the instant replay function.
  432. 16 The dispatch console shall have the ability to monitor a minimum of 50 audio sessions (talkgroups, repeaters, telephones, etc.) at the same time. The dispatch console sub-systems shall support three separate telephone systems.
  433. 17
  434. 18 The console subsystem shall allow the user the flexibility to personalize the operator position. Authorized personnel shall be able to change at a minimum:
  435. 19 • Assignment of names for each key functions
  436. 20 • Assignment of names for each module graphics
  437. 21 • Assignment of active display color
  438. 22 • Screen layout according to individual operator preference
  439. 23 • Assignment of access to selected talkgroups, channels, paging and phone lines
  440. 24
  441. 25 The minimum console functions accessible by dispatchers shall include:
  442. 26 • Select, control and transmit at any phone line, channels or talkgroups or combination of
  443. channel/talkgroups available at that position
  444. 27 • Access channels, talkgroups, phone lines and other consoles by a one (1) button/switch
  445. 28 • Monitor any combination of channels and talkgroups authorized
  446. 29 • Patch any combination of channels, talkgroups and phone lines authorized by using just one (1) RF channel
  447. 30 • Alert the dispatcher by a tone that a channel becomes available and hold it for the dispatcher for two (2)- four (4) seconds
  448. 31 • Mute all unselected audio for preset time
  449. 32 • Display unit and alarm indicators on specific channels/talkgroups
  450. 33 • Enable or disable conventional base or repeaters or selective auxiliary functions
  451. 34 • Select main or standby conventional base or repeaters
  452. 35 • Have instant access to any channel and talkgroups, whether selected or not
  453. 36 • Able to make private calls to any field unit(s), phone lines, and consoles as authorized
  454. 37 • Able to support transmitting three individual alert tones to individuals or groups
  455. in simulcast mode, zone mode or sequential (cascade) mode
  456. 38 • Able to automatically interface with the existing Intergraph Computer Aided Dispatch
  457. (CAD) system
  458. 39 • Able to monitor and transmit in multiple encrypted channels, phone lines and talkgroups
  459. 40 • Patch set up control
  460. 41 • Simultaneously select and transmit multiple talk groups and other configured resources
  461. 42 • Alert tone selectors
  462. 43 • All mute switch with programmable option
  463. 44 • Master push to talk selected channels
  464. 45 • Monitor switch conventional channels
  465. 46 Proposal Location
  466. 47 All consoles shall be capable of providing each operator with its own unique template that can be designed, saved and retrieved.
  467. 48 The console template configurations shall be able to be backed-up on external hard drives, CDs, DVDs, or other appropriate media, so they may be transferred between operator positions.
  468. 49
  469. 50 The following radio operations shall be available while a new screen display is being configured:
  470. 51 • Select and unselect audio can be heard
  471. 52 • Auxiliary input alarms can be heard and reset
  472. 53 • Emergency tones can be heard and reset.
  473. 54
  474. 55 The dispatchers shall be able to determine the following channel display capabilities through the console screen:
  475. 56 • Alpha-numeric channels/talkgroups names
  476. 57 • Whether channels are available in each screen configuration
  477. 58 • Whether audio is heard and call and busy indications are seen when in the channel
  478. summary list
  479. 59 • Whether a channel shall always be displayed as a channel control window and cannot be
  480. removed from the radio work area
  481. 60 • Which, if any, color border shall appear around a channel control window, these color
  482. borders can be used to group associated channels.
  483. 61
  484. 62 The graphic module, at a minimum, shall provide the dispatcher with the following information:
  485. 63 • Name for each channel/talkgroup
  486. 64 • The screen shall display "Select" (SEL) at the dispatch position and shall remain lit displayed until another channel/talkgroup has been selected on the dispatch position
  487. 65 A display indicator that includes Unit ID or Alias shall appear when receiving messages from subscribers at the channel/talkgroup icon. The same light indication shall flash even if the channel becomes active while unselected
  488. 66 • A "Busy", with transmitting console alias indication, shall appear on all consoles with
  489. talkgroup icon displayed when another dispatch position has placed the channel/talkgroup
  490. in transmission mode
  491. 67 • Voice volume indication for both transmit (eg. "VU Meter") and receive (eg. "volume level
  492. bar graph in each talkgroup icon") at each console
  493. 68 • A different colored indicator shall be used to indicate the selection of the mute mode
  494. 69
  495. 70 The console terminal shall utilize a touch-screen monitor with a minimum:
  496. 71 • Shall be burn-in resistant
  497. 72 • Viewing area of 21” diagonal
  498. 73 • Direct control of all console functions by touching the appropriate control graphic
  499. 74 • Anti-reflective overlay shield to protect the screen face from contamination from
  500. fingerprint oils and perspiration
  501. 75 • Response to only a single finger touch
  502. 76 • Both touch-screen and mouse control simultaneously
  503. 77
  504. 78 The terminal shall be equipped with a dispatch button keyboard capable of being connected for intermittent use.
  505. 79 An intercom function shall be provided on the screen to permit the console operator to selectively talk to another console connected to the central electronics switch. There shall be no limit to the number of mutually exclusive intercom conversations that may be carried on simultaneously. This intercom connection shall not be connected to the instant play back system.
  506. 80 Each console position shall have access to instant recall functions from the digital voice recorder or an equivalent stand-alone unit.
  507. 81 An interface to control an instant central recall recorder shall be provided at each dispatcher position. The instant recall recorder shall be wired to record the console telephone (9-1-1 and business lines) audio, designated talkgroups, and channels to be selected later. The recorder shall replay that audio upon demand from any console through the unselect speaker, muting the unselect audio during playback.
  508. 82 A hard-drive or similar media shall be incorporated in the Instant Playback module to provide a minimum of 30 minutes of recording time for each console position.
  509. 83 Each channel or talkgroup control window shall display the name of the channel or talkgroup with which it is associated that shall be configurable by authorized personnel through the setup function. The operator shall not be required to associate numbers with a channel to perform any function.
  510. 84
  511. Subscribers
  512.  
  513. A B C D
  514. 1 ATTACHMENT 005 SUBSCRIBERS - CROSS REFERENCE MATRIX
  515. 2 SUBSCRIBERS Proposal Location
  516. 3 General Requirements
  517. 4 All subscriber radios shall be capable and equipped to support at a minimum the following features:
  518. 5 • Capable of operation from 136 MHz to 174 MHz
  519. 6 • 128 talk-groups and 200 conventional channels.
  520. 7 • Capable of concurrently supporting digital and analog operation
  521. 8 • Emergency alarm button with channel revert and acknowledgement
  522. 9 • Out of range indicator with programmable enunciation (visual and audible) parameters
  523. 10 • Radio Stun/Kill
  524. 11 • Capable of storing a minimum of ten (10) different encryption keys used on different talkgroups/channels
  525. 12 • Shall have a screen display capable of verbose indicators of user
  526. input and radio condition.
  527. 13
  528. 14 Subscribers shall have the following minimum end-user programmable features (without the use of OTAR, OTAP or a PC):
  529. 15 • High and Low Power
  530. 16 • Display Backlighting Settings from Dim to Bright
  531. 17 • Talk-around
  532. 18 • Encrypted digital modes
  533. 19 • Clear Transmissions
  534. 20 • Scan and similar modes of operation which can be configured to meet
  535. user demands
  536. 21
  537. 22 All subscriber radios must have an on/off switch to activate or deactivate the encryption ability of the radio per talk group or conventional channel. Encryption shall be either operator selected or preconfigured on a per talk group basis by radio programming.
  538. 23 All subscriber radios must have the ability to scan up to a minimum of ten (10) operator selectable talk groups with a minimum of three levels of priority.
  539. 24 All screen controls and indicators shall have auto-brightness control rendering the display visible in direct sunlight and visible in complete darkness with operator capability to turn all lights off.
  540. 25 All subscriber radios proposed shall be fully operationally functional, affiliated and able to transmit voice traffic through the system, within 2 seconds of being powered on.
  541. 26 All subscriber units shall have a display that at a minimum, reflects channel information, out of range indication, and channel status information
  542. 27 All subscriber units shall utilize Encryption AES-256 FIPS 140-2, level 2, type 3.
  543. 28 Whenever a field unit leaves the radio coverage area or is out of contact with the control/signaling channel, an audible alert shall be sounded automatically. The subscriber shall be equipped with programmable enunciation (visual and audible) parameters.
  544. 29 Mobile Radio Technical Requirements
  545. 30 All mobile radios shall meet the following minimum requirements:
  546. 31 Transmitter Technical Specifications:
  547. 32 • Vehicle RF power output of 100 Watts adjustable down the 25 Watts
  548. 33 • Motorcycle RF output a minimum of 25 Watts
  549. 34 • Mobile subscriber must allow power to be reduced to 25 watts without
  550. the aid of an attenuator.
  551. 35 • Operate on 13.8 VDC
  552. 36 • Frequency Stability 2.0 Parts Per Million (PPM)
  553. 37 • Spurious Emissions -80 dB or greater
  554. 38 • Adjacent Channel Suppression -70 dB or greater
  555. 39 • VDC Current draw maximum 25 Amps
  556. 40
  557. 41 Receiver Technical Specifications:
  558. 42 • Intermodulation -80 dB or greater
  559. 43 • Spurious Rejection -80 dB or greater
  560. 44 • Selectivity -70 dB or greater
  561. 45 • Sensitivity .25 Uv or greater @ 5% BER
  562. 46 • Frequency Stability 2.0 PPM
  563. 47 • Audio Distortion 3% or less at full deviation
  564. 48 Proposal Location
  565. 49 All mobile radios shall have a weatherproof microphone.
  566. 50 All mobile radios for motorcycles shall have a weatherproof, water resistant package, noise canceling weatherproof microphone
  567. 51 Mobile antenna shall be ¼ wave length for the 136-174 MHz range and shall utilize a ž” hole mounting style with a minimum of 17’ of coaxial cable and be capable of radiating at 100 Watts.
  568. 52 The mobile radio shall have an accessories port for connections to external audio, logic, control, ignition sense, emergency closure and or data implementations.
  569. 53 The mobile radio installation options shall support remote mount control head, multiple control head, handheld control head, and be equipped to accommodate all these installation styles which shall also include covert installations (the majority of required devices will be remote mount single control heads).
  570. 54 The mobile radio shall have a speaker with a minimum of 10 watts audio output
  571. 55 Control Head
  572. 56 The mobile radios shall provide waterproof remote control heads suitable for remote mounting on a motorcycle.
  573. 57 External Speaker
  574. 58 The mobile radio shall have external speakers that shall have a minimum of 10-Watts audio.
  575. 59 Mobile radios shall have a weatherproof speaker (speaker and cable) for use in specialized vehicles.
  576. 60 Standalone High Power Vehicular Mobile Repeater Technical Requirements
  577. 61 The mobile repeaters shall meet the following minimum requirements:
  578. 62 Transmitter Technical Specifications:
  579. 63 • RF power output 30-110 Watts adjustable range
  580. 64 • Frequency range 150-174 MHz
  581. 65 • Audio distortion less than 2% at rated audio @1000Hz
  582. 66 • Frequency stability 1PPM (-22 degrees F to 140 degrees F)
  583. 67 • Modulation Limiting <+2.5 kHz at 12.5 kHz channel spacing
  584. <+5.0 kHz at 25 kHz channel
  585. 68 • Duty Cycle 100% continuous transmit operation
  586. 69 • Adjacent Channel Power -70dB @ 12.5kHz
  587. 70 • RF impedance 50Ω
  588. 71 • Spurious Attenuation 90dB or better
  589. 72
  590. 73 Receiver Technical Specifications:
  591. 74 • Frequency range 150-174MHz
  592. 75 • Channel spacing <+25 kHz/12.5kHz
  593. 76 • Frequency stability 1PPM (-22 degrees F to 140 degrees F)
  594. 77 •Sensitivity -20 dB quieting < 0.5uV
  595. 78 -12 dB SINAD < 0.25uV
  596. 79 • Selectivity > -75 dB/12.5 kHz
  597. 80 • Audio output 4 Watts
  598. 81 • Intermodulation rejection -75 dB min.@12.5 kHz
  599. 82 • Spurious response 100 dB
  600. 83 • RF impedance 50 Ω
  601. 84
  602. 85 The mobile repeater shall accept a minimum of nominal 24 VDC power for all operations.
  603. 86 The mobile repeater, with its duplexer, shall occupy space within the vehicle that shall be limited to the rear of the middle seat in a SUV. The equipment shall be located into a vented enclosure with a 15" depth 48" width and 30" height
  604. 87 The mobile repeater shall have an operating temperature range of -22° F to 140° F.
  605. 88 The mobile repeater shall operate into a single antenna and equipped with a duplexer that shall provide a minimum of 90 dB isolation RX to Tx along with an overall insertion loss of less than 2.0 dB .
  606. 89 The mobile repeater antenna shall be deployable on a moving vehicle operating at vehicle speeds in excess of 100 mph.
  607. 90 The mobile repeater shall be fully configurable via software and portable computer with the capability of remote connection via IP connection (remote access) which would include channel configuration, mode of operation, and diagnostics of the repeater while in operation.
  608. 91 The mobile repeater shall be equipped for a minimum capacity for ten frequency pair or RF channels selectable only via programming software.
  609. 92 The mobile repeater shall be equipped with the following frequencies to be used one at a time:
  610. 93 • Travel 1: TX 168.350 RX 163.100 NAC Code TBD
  611. 94 • Travel 2: TX 173.525 RX 166.450 NAC Code TBD
  612. 95 • Travel 3: TX 173.875 RX 166.475 NAC Code TBD
  613. 96 The mobile repeater shall be equipped with a control head to operate repeater functions and be equipped with a speaker and microphone for local operator use.
  614. 97 The mobile repeater shall be equipped with a 600 Ω balanced two way interface and PTT for connection to an audio switch.
  615. 98 The mobile repeater shall be equipped to operate in digital mode.
  616. 99 The mobile repeater shall be equipped to transparently repeat AES 256 bit encrypted traffic as configured by subscriber traffic.
  617. 100 The mobile repeater shall be equipped with the ability to decode and encode AES 256 bit encrypted traffic for local transmit and receive audio and be equipped with a key loading port.
  618. 101 Portable Radio Technical Requirements Proposal Location
  619. 102 The portable radios shall meet the following minimum requirements:
  620. 103 Transmitter Technical Specifications:
  621. 104 • RF output power 5 watts minimum
  622. 105 • Frequency Stability to within < ±2.5 PPM (-22° F to +140° F)
  623. 106 • Spurious Emissions >-70 dB
  624. 107
  625. 108 Receiver Technical Specifications:
  626. 109 • FM Noise and Hum >-45 dB or greater
  627. 110 • Frequency Stability <2.5 PPM (-22° F to +140° F)
  628. 111 • Intermodulation Rejection >-70 dB or greater
  629. 112 • Spurious Rejection >-70 dB or greater
  630. 113 • Selectivity >-60 dB or greater
  631. 114 • Overall Sensitivity > .25uv @ 60% deviation
  632. and/or 5% bit error rate
  633. 115 • Audio Output Min. 500 mw @ max deviation
  634. full volume
  635. 116
  636. 117 The portable radios shall have an accessory adaptor connector design that mitigates fluid entry into the radio internal components.
  637. 118 All portable radios shall have a programmable keypad lock.
  638. 119 Portable radios shall have a noise canceling speaker microphone, weatherproof with the capability for a connection from a surveillance ear piece to the speaker microphone assembly.
  639. 120 All portable radios and batteries shall be Factory Mutual (FM) intrinsically safe, lithium ion composition.
  640. 121 A three position switch located on the top of the radio shall be user programmable. Minimum modes of operation shall be talk-around, monitor, scan and zone select
  641. 122 All portable radios shall incorporate slip resistant case material conducive to firm and secure gloved hand operation.
  642. 123 Portable radio batteries must operate radio for a minimum of nine (9) hours assuming a 10% transmit, 10% receive and 80% standby mode duty cycle.
  643. 124 Control Station
  644. 125 The control station shall meet the following minimum requirements:
  645. 126 Transmitter Technical Requirements:
  646. 127 • 136-174 MHz Full bandwidth
  647. 128 • RF Output Output of 100 Watts adjustable down to 25 Watts
  648. 129 • Frequency Stability 2.0 PPM
  649. 130 • Spurious Emissions -80 dB or greater
  650. 131 • Adjacent Channel Suppression -70 dB or greater
  651. 132 • VDC Current draw Shall not exceed 25 Amps
  652. 133
  653. 134 Receiver Technical Requirements:
  654. 135 • Intermodulation -80 dB or greater
  655. 136 • Spurious Rejection -80 dB or greater
  656. 137 •Selectivity -70 dB or greater
  657. 138 • Sensitivity .25 Uv or greater @ 5% BER
  658. 139 • Frequency Stability 2.0 PPM
  659. 140 • Audio Distortion 3% or less at full deviation
  660. 141 Proposal Location
  661. 142 The control station must be configurable to operate in the both local and remote mode simultaneously.
  662. 143 The control station shall have a desk microphone with PTT connected through a port on the front of the enclosure for local operation and a built in speaker in the console housing.
  663. 144 The control station shall have the ports and connections to allow for remote operations from a deskset located away from the control station connected via copper wire and a network style connector.
  664. 145 The control station shall have the ports and connections to allow for remote operations tone control from a desk set.
  665. 146 The control station shall have a configurable TX / RX tape out port capable of 600 Ω or high impedance interfaces.
  666. 147 The layout of the control station shall be in an enclosure suitable for use on an office desk.
  667. 148 The control station shall be powered for 100% transmit duty cycle 120VAC or 12VDC power supply through external ports from the enclosure.
  668. 149 The control station shall have a control head capable of controlling all programmed features.
  669. 150 The control station shall have a speaker located in the front with the capability via software programming to control the minimum volume and maximum volume in addition to the volume control from the radio control head.
  670. 151 The control station shall have an external connection for key loading.
  671. 152 The desk set manipulation of the control station shall include, but not be limited to PTT, transmit audio, receive audio, and talkgroup/channel selection and display information that include, user ID's, talkgroup status, emergency ID information, etc.
  672. 153 The control station shall allow for the installation of a headset jack and a foot activated PTT switch.
  673. 154 The control station local control head shall have a display that, at a minimum, will display channel information, out of range indication, channel status information, and similar messages to the user.
  674. 155 The control station shall be mountable in a 19” EIA standard rack.
  675. 156
  676. 157
  677. 158
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement