Amendment 2 Attachment B - Technical Requirements.xlsx
XLSX spreadsheet 23 KB Posted
- Attached to
- Communications Recording Logger
- Solicitation number
- CR-308027
View the file
Other files
Show all 14
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Requirements
| Attachment B | ||
| Technical Requirements | ||
| (A) | ||
| Req. Id | (B) | |
| Domain Area | (C) | |
| Description | (D) | |
| Type of Requirement | (E) | |
| Priority | (F) | |
| Conforms (Y/N) | (G) |
Reference to Proposal Page #
| 1 | Technical | Communications loggers shall record digital PBX telephones, VoIP telephones, analog telephones, analog C.O. lines, CAMA trunks, analog radio audio, T1 & E1 trunks, ISDN-PRI trunks, ISDN30 trunks, SIP trunks, IP-dispatch consoles (AVTEC, Telex, Zetron, and others), Radio over IP (RoIP), trunked and conventional 2-way radio, Motorola ASTRO 25 radio with AIS, EF Johnson P25 radio, ED137B/C ATC IP, PC Screens, and more. | Functional | Must-have |
| 2 | Technical | The communications recording logger shall communicate with the existing Intrado Viper System. | Functional | Must-have |
| 3 | Security | Password policy options shall include complexity enforcement, automatic aging, change reminders, expiration, and lock-out. | Functional | Must-have |
| 4 | Capacity | The communications logger shall be field upgradeable from 8 to 120 digital PBX telephone channels, 8 to 120 analog channels, 8 to 560 VoIP/RoIP channels, 8 - 560 NG9-1-1 SIPREC channels, 24 - 192 T1/PRI channels, 30 - 240 E1 channels, 8 - 120 P25 channels, or 8 - 560 DMR channels | Functional | Must-have |
| 5 | Technical | A wide range of mixed channel quantities (digital + analog + VoIP/RoIP, etc.) shall be accommodated within a single logger. | Functional | Must-have |
| 6 | Storage | Communications Recording Loggers shall include a standard multidrive for DVD-RAM archiving (9.4GB per dual-sided DVD-RAM disk, for 1540 hours at 13kbps). | Functional | Must-have |
| 7 | Storage | Archiving shall not affect any ongoing recording operations | Functional | Must-have |
| 8 | Software | Accessing software for replay shall not in any way affect the recording process | Functional | Must-have |
| 9 | Standards | Communications logging systems should/must be designed to conform to the NENA i3 standard for recording of NG9-1-1 primary interactions via the SIPREC method. | Functional | Should-have |
| 10 | Recording | It should also have the option to record the EF Johnson ATLAS P25 radio system, Harris Vida P25 and TAIT P25. | Functional | Should-have |
| 11 | Resilience | Communications loggers should offer multiple levels of resilience, including redundant power supplies, redundant hard disk drives (with choices of RAID levels 1, 5, or 10 connectivity), redundant network capability (via NIC bonding), and multiple choices for archive redundancy and network-based archive storage. | Functional | Should-have |
| 12 | Resilience | The communications loggers should be equipped with dual hot-swap load-sharing 120/240 VAC power supplies. | Functional | Should-have |
| 13 | Security | Communications Logging Recorders should include a multi-tier security system that controls user access based on role and channel (or talk group) assignments; the logging software designed to enhance security by encouraging users to employ strong passwords and to use them properly. | Functional | Should-have |
| 14 | Security | In addition, each user’s access and actions should be audited and available for review. | Functional | Should-have |
| 15 | Capacity | Recorders should be easily combined to provide recording solutions for higher channel counts, multiple sites, and/or redundancy. | Functional | Should-have |
| 16 | Capability | In addition to recording audio and PC screen media, communications logging recorders should support integration to a variety of metadata sources that provide call-associated information. | Functional | Should-have |
| 17 | Storage | Communications Recording Loggers should include an internal RAID array of hard disk drives for reliability and redundancy. | Functional | Should-have |
| 18 | Storage | Offerings should range from a standard pair of 1 Terabyte hard drives with RAID-1 (providing 1 Terabyte of storage for up to 166,000 hours @13 kbps compression) all the way up to four hot-swap 4 Terabyte hard drives with RAID-6 (providing 12 Terabytes of storage for up to 2 Million hours @13 kbps compression). | Functional | Should-have |
| 19 | Capability | Communications Recording Loggers should include an archiving utility which enables archiving of all recordings and metadata | Functional | Should-have |
| 20 | Features | Software should be browser-based to provide enhanced recording management capabilities including flexible search, multiple-call replay, graphical time-line with pan/zoom, variable-speed replay, incident management tabs, audio redaction, audio waveforms, talking time/date, call protection, burning of calls or incidents to CD/DVD/Blu-Ray, export or email incident, live monitor and instant recall. | Functional | Must-have |
| 21 | Features | The software should provide dispatchers and supervisors with preset-based instant recall, variable-speed replay, record-on demand, text annotation, and export to WAV file | Functional | Should-have |
| 22 | Features | In addition, the software should provide rich instant recall capabilities from a browser. | Functional | Should-have |
| 23 | Hardware | The communications recording logger should have a color front touch screen to view the current status of each channel and each archive, receive visual and audible alerts, live-monitor multiple channels, and fully administer the system using provided Configuration Manager software | Functional | Should-have |
| 24 | Software | Communications recording loggers should include Configuration Manager software, which permits secure browser-based access to system configuration parameters. | Functional | Should-have |
&12Attachment B &UFunctional and Technical Requirements Employee Concerns Hotline and Ethics Incident Management System&U
&12RFP CR-308027
&"-,Bold"
May 29, 2020 &P of &N
Look-up List
| Must-have |
| Should-have |
| Could-have |
| Will not have |
File details come from the government source that posted it. Updated .