SOURCES SOUGHT
58 -- REQUEST FOR INFORMATION FOR COMMERCIALLY AVAILABLE COMMERCIAL RADIO CONTROL SYSTEMS (RCS)
- Notice Date
- 3/8/2016
- Notice Type
- Sources Sought
- NAICS
- 334220
— Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
- Contracting Office
- Department of Homeland Security, United States Coast Guard (USCG), C4IT (C3CEN), Coast Guard Blvd, Portsmouth, Virginia, 23703, United States
- ZIP Code
- 23703
- Solicitation Number
- HSCG44-16-R-RFO0010
- Archive Date
- 4/26/2016
- Point of Contact
- Katherine Marie Kearney, Phone: 7572952280
- E-Mail Address
-
katherine.m.kearney@uscg.mil
(katherine.m.kearney@uscg.mil)
- Small Business Set-Aside
- N/A
- Description
- REQUEST FOR INFORMATION FOR COMMERCIALLY AVAILABLE COMMERCIAL RADIO CONTROL SYSTEMS (RCS) HSCG44-16-R-RFI0010 Disclaimer and Important Notes: This posting is a Request for Information (RFI) from interested vendors and is issued solely for informational and planning purposes. This posting is not a Request for Proposals or a Request for Quotations, and it is not considered to be a commitment by the Government to award a contract nor is the Government responsible for any costs incurred in furnishing information provided under this RFI. No basis for claim against the Government shall arise as a result from a response to this RFI or Government use of any information provided. Further, the Coast Guard is not at this time seeking proposals and will not accept unsolicited proposals. No proprietary, classified, confidential, or sensitive information should be included in your response to this RFI. The Government reserves the right to use any information provided by respondents for any purpose deemed necessary and legally appropriate, including using technical information provided by respondents in any resultant solicitation. Responses will assist the Government in determining the availability of potential solutions and commercial products in the market. At this time no solicitation exists; therefore, do Not Request a Copy of the Solicitation. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement. REQUIREMENT: The Department of Homeland Security, U.S. Coast Guard, Command, Control, and Communications Engineering Center (C3CEN) requests information on the availability of commercial Radio Control Systems (RCSs). The RCS consists of Operator Consoles and a Radio/Console Control and an Audio Route/Record/Replay Subsystem. USCG C3CEN is seeking a commercial vendor to provide the RCS, integrate standards compliant radios, and deploy RCS at sectors and stations. The RCS must be capable of integrating the following TIA-102.BAHA standards- compliant base stations that include non-BAHA messages supporting Over-The-Air-Rekeying (OTAR): 1. Mixed mode (analog wideband and digital/analog narrowband) VHF base stations 2. Narrowband UHF digital and analog base stations An Interface Control Document will be provided to support integration of the RCS with base stations. The RCS and the base stations are planned to be procured under separate solicitations. Deployment of the new Radio Control System will occur after installation of base stations. Part of the requirement will include working with a third party to cut over (soft cut over) to the RCS in order to reduce operational risk. A soft cutover will allow base stations to be quickly cut back to the existing radio control system if problems are encountered with the new RCS. Operator Consoles will be installed at operational Coast Guard sectors and stations (32 sectors and 168 stations) located in the continental United States, Puerto Rico, Hawaii, and Guam. The Radio/Console Control and Audio Route/Record/Replay Subsystem will be installed at a subset of sector sites and at two (2) test sites. RCS will reside on the Coast Guard's CGOne network, so initial and ongoing support for Information Assurance is critical (see NIST 800-53 https://web.nvd.nist.gov/view/800-53/home ). The RCS must meet the performance requirements listed below. PERFORMANCE REQUIREMENTS 1. User Authentication & Microsoft Active Directory Integration The RCS shall be capable of being integrated with the USCG's enterprise information system management environment (USCG Microsoft Active Directory) and shall require users and administrators to authenticate at log-in using USCG-issued Common Access Cards (CAC). 1.1. Operator Console Locking. The system shall prevent the Operator Console from locking during periods of inactivity or removal of a user's CAC. 1.2. User Log-in Agreement Banner. The system shall be able to display the USCG user agreement banner at log-in. 1.3. Operation during Log-out/Log-in. The Operator Console shall be able to continue to receive audio, provide audio through speakers, and record audio during user log-out/log-in at the beginning and end of each watch stander's duty period. 2. Information System Security The system will be characterized as Moderate-Moderate-Moderate for Confidentiality, Integrity, and Availability per the Federal Information Processing Standard (FIPS) 199. The Operating Systems for all workstations and servers shall be capable of being configured according to applicable Security Technical Implementation Guides (STIGs): • Windows 10 Version 1, Release 2 (01 FEB 2016), or latest version, posted at: http://iase.disa.mil/stigs/os/windows/Pages/index.aspx • Windows Server Version 2, Release 3 (23 OCT 2015), or latest version, posted at: http://iase.disa.mil/stigs/os/windows/Pages/index.aspx 2.1. Operating System Patches and Antivirus Updates. The system shall allow a system administrator to remotely update and patch operating systems and antivirus tools and manually reboot servers and workstations from within the CGOne network. 2.2. Enterprise Services. System operator consoles and servers shall be compatible with Coast Guard enterprise SCCM 2012 patch management and Host-Based Security System (HBSS) services (see http://www.disa.mil/hbss). HBSS consists of McAfee host intrusion prevention and anti-virus software clients. 3. Radio Control System Capacities 3.1 Operator Consoles. The RCS must support a minimum of 60 non-collocated (network-connected) Operator Consoles (sector or station, see sections 4 & 5) with a single Radio/Console Control and Audio Route/Record/Replay Subsystem. 3.2 Radios. The RCS must integrate and support a minimum of 300 (qty) TIA-102.BAHA compliant VHF and UHF base stations with a single Radio/Console Control and Audio Route/Record/Replay Subsystem. 3.3 Network Capacity. Operator consoles, base stations, and the Radio/Console Control and Audio Route/Record/Replay Subsystem will be primarily non-collocated. Information on network throughput requirements for the total number of radios and operator consoles is required. 4. Radio/Console Control and Audio Route/Record/Replay Subsystem Redundancy 4.1. Redundancy. The RCS must include non-collocated, hot standby redundancy for the Radio/Console Control and Audio Route/Record/Replay Subsystem, supporting continued operation of consoles and Remote Fixed Facility (RFF) radios when the primary Radio/Console Control and Audio Route/Record/Replay Subsystem is inoperative or network connections fail. 4.1.1. Capability Description. Hot standby capabilities, switching time, and switching method must be described sufficiently to understand the impact on capabilities and operations. 4.1.2. Effect on RFFs. If modifications are required at RFFs to support redundancy, describe those modifications, their installation procedures, and any impact on operations during installation. 4.1.3. Effects on Interfaces. If modifications are required at RFFs to support redundancy, describe the effect of those modifications on the TIA-102.BAHA and OTAR interface between the Radio/Console Control and Audio Route/Record/Replay Subsystem and RFFs. 5. Record/Replay 5.1. General. The system shall record and provide a means to playback, at each operator console, all transmitted and received communications for the previous 30 days. 5.2. Unencrypted Recordings. The system shall record all voice transmissions in an unencrypted audio format. 5.3. Instant Playback. The system shall provide a means to replay the last received call or any call during a user selectable time interval within the last 30 minutes. 5.3.1. Instant Playback Response. The system shall initiate the replay of a selected transmission within one (1) second of selecting the call. 5.4. Playback Sorting. The system shall allow the operator to sort recorded calls by date/time, RFF, and channel. 5.4.1. Playback Sorting Response. The system shall re-sort the recorded calls list within one (1) second of operator command. 5.5. Archiving. The system shall allow the operator to select one or more recorded calls for archiving to non-flash portable media, such as compact disk (CD) or digital video disk (DVD). 5.6. Timestamp. The system shall timestamp all recordings. Timestamp precision shall be one second or better. 5.7. Digital Voice Logger Integration. The Coast Guard has a requirement to provide an interface control document to a third party for integration of digital voice logging capabilities (ability to independently search for and retrieve recorded audio). Please elaborate on the ability/willingness of your company to enter into a non-disclosure with a third party. 6. Operator Consoles 6.1. Sector Operator Consoles. The RCS must include multiple operator consoles (i.e. 3-4) at each of thirty-two (32) Sector Command Centers (SCCs). 6.1.1. Sector Operator Console RFF Capacity. Each Sector Operator Console shall have the capacity to transmit/receive and change channels on all radios at a minimum of twenty (20) RFFs (5 radios per RFF). 6.1.2. Speakers. Each Sector Operator Console shall provide a minimum of six (6) speakers. At least one speaker in the Sector Operator Console shall be capable of monitoring all base stations assigned to the Operator Console. RCS shall support assignment of one or more base stations to the other speakers. 6.1.3. Foot Pedal. Each Sector Operator Console shall provide a dual action foot pedal to key the microphone and mute all speakers. 6.1.4. Headsets. Each Sector Operator Console shall be provisioned with a wired headset with push to talk button, microphone, and headphones. Wireless headsets cannot be used in sectors. 6.2. Station Operator Consoles. The system shall include one (1) Station Operator Console at each Coast Guard station. 6.2.1. Station Operator Console RFF Capacity. Each Station Operator Console shall have the capacity to transmit/receive and change channels on all radios at a minimum of ten (10) RFFs (5 radios per RFF). 6.2.2. Speakers. Each Station Operator Console shall provide a minimum of four (4) speakers. At least one speaker in the Station Operator Console shall be capable of monitoring all base stations assigned to the Operator Console. RCS shall support assignment of one or more base stations to the other speakers. 6.3. Operator Console Intercom. The system shall provide separate intercom capabilities between SCCs and between the SCC and its subordinate stations. 6.4. Visual Indication. Operator Consoles shall provide a visual indication of which RFF is transmitting or receiving a signal. 6.5. Manual Muting. Operator Consoles shall be capable of manually muting all speakers upon command by the operator. Manual mute shall automatically un-mute after 30 seconds. 6.6. Cross-muting. The RCS shall provide a cross-muting capability to support muting of adjacent base stations when transmitting on a common frequency. 6.7. Time-out. Operator consoles shall be capable of "timing-out" to prevent unnecessary or unwanted transmissions (e.g., stuck key). 6.8. Operator Console Configuration. Configuration of an Operator Console shall be restricted to a system administrator user role. 6.8.1. Administrative Control of RFFs. Selection of which RFFs are monitored by an operator console shall be restricted to a system administrator user role. 6.8.2. Administrative Control of Frequency Selection. Configuration of frequencies available for selection by an operator during channel changes shall be restricted to a system administrator user role. The USCG will use this capability to ensure that one radio always remains on channel 16. 6.8.3. Speaker Configuration. Assignment of RFFs to operator console speakers shall be restricted to a system administrator user role. 7. Encryption The RCS, when integrated with tech refreshed base stations, shall provide FIPS Pub 140-2 compliant encryption capabilities including FIPS-197 compliant Advanced Encryption Standard (AES) and Digital Encryption Standard (DES) encryption of "Over the Air" communications on P25 Phase 1 digital channels in the Federal Land Mobile Radio band. 7.1. Multi-Key Encryption. The system shall store a minimum of twenty-seven (27) unique encryption keys for separate missions. 7.2. User Selectable. The system shall allow the operator to select the encryption mode (clear/protected) and encryption key. 7.3. Encryption Mode Indicator. The system shall provide a visual indicator to the operator identifying whether transmitted or received calls are encrypted or in the clear 8. Key Management Facility (KMF). The RCS is currently configured to receive P25-compliant encryption key material over the network from a Motorola Key Management Facility (Motorola KMF Server, KMF Client version 7.14.0033) installed and operated at the US Customs and Border Protection (CBP) National Law Enforcement Communications Center (NLECC). If the proposed Base Station is not compatible with current Motorola equipment, the system shall be compliant with other vendor commercial KMF equipment (provide details on the commercial KMF system that affords compatibility). 8.1. Over The Air Re-Keying. The system shall be capable of receiving Key Management Messages (KMMs) generated by the CBP NLECC and distributing the KMMs to mobile subscriber units. If not compatible with the Motorola equipment, the system shall be compliant with other vendor commercial KMF equipment (provide details on commercial KMF compatibility). 8.2. Encrypted Communications Compatibility with USCG Standard Mobile Radios. The system shall be compatible with Project 25 (P25) mobile and portable radios which support both Digital Encryption Standard (DES) and Advanced Encryption Standard (AES) encryption. All radios conform to the TIA-102.AACA-A Project 25 Digital Radio Over-the-Air Rekeying (OTAR) Protocol. 9. RFF Monitoring. The RCS shall monitor sensors at the RFFs and display status at the SCC Operator Consoles. The system shall provide a visual and audible alarm if the statuses of RFF sensors change as well as a means of acknowledging and resetting the alarm. The system shall record sensor values for a minimum of 30 days to support trend analysis. The system shall also provide remote access by maintenance personnel external to the Operator Console to support fault location and identification. 9.1. Intrusion Detection. For RFFs where the Coast Guard is the sole occupant of a shelter, the RFF Site Monitoring System shall alarm when the shelter door is opened. For RFFs where the equipment is in a shared space, the RFF Site Monitoring System shall alarm when the equipment cabinet access door is opened. 9.2. High/Low Temperature. The RFF Monitoring System shall alarm when the RFF is above or below its normal temperature range. 9.3. Fire/Smoke Alarm. The RFF Site Monitoring System shall alarm when smoke is detected in the RFF. 9.4. Utility Power. The RFF Site Monitoring System shall indicate whether the site is operating on normal utility power or an emergency back-up power supply. 9.5. Radio Fault Monitoring. The system shall indicate the operational status of the RFF radios including any built-in self-diagnostic fault monitoring capability of the RFF site radios. 9.6. Generator Status. The system shall indicate the status of the RFF generator. 9.7. Generator Fuel Status. The system shall provide information on the level of propane or diesel and generate an alarm when tank is < ¼ full. 9.8. Consumable Real-Time System Status Information. The RCS shall provide real-time system operating status information, and RFF monitoring sensor status, in one of the consumable formats listed below: • Coast Guard Enterprise Service Bus (ActiveMQ-based) • Kml • Shapefile 10. Telephone Interface (sector only) The RCS shall provide a minimum of one telephone line interface at each sector Operator Console. The telephone interface shall allow the operator to dial and receive telephone calls on the Public Switched Telephone Network (PSTN) via an existing PBX collocated with the Radio/Console Control and an Audio Route/Record/Replay Subsystem (primary and back up). 10.1. Call History. The telephone interface shall provide a list of a minimum of the last ten dialed and received telephone calls. 10.2. Contact List. The telephone interface shall include a contact list to store a minimum of one hundred frequently used telephone numbers. 10.3. Caller ID. The system shall display the telephone number and identification of incoming calls as available from the call if the number is stored in the contact list. 11. Circuit Management 11.1. Coverage Overlap Muting. The system shall be configurable to mute received audio from RFFs whose receive coverage area overlaps with the transmit coverage area of a transmitting RFF. 11.2. Network Latency Compensation. Provide information on how the proposed system can be configured to compensate for fixed network latency (latency increases when RFFs lose landline connections and switch to back up VSAT network connections) between the RFFs and the operator consoles in order to minimize echoes when calls are received or transmitted by two or more RFFs. 11.3. Transmit Groups. The system shall allow the operator to configure transmit groups in order to transmit from multiple RFFs at once, up to all RFFs assigned to the operator console. 11.4. Patches. The system shall allow the operator to configure patched circuits between two or more radios at geographically separated RFFs, between two or more radios on different frequencies, and between one or more radios and a telephone line. 11.5. Volume Control. The system shall allow the operator to set the volume on each speaker, telephone, and intercom circuit. 12. Automatic Broadcast Notice to Mariners The system shall provide the ability for an operator to pre-record broadcast information and select the RFFs, radio frequency, times, and periodicity to automatically transmit the message. 12.1. Text to Audio. The system shall provide the ability to enter an automated broadcast message as text and convert the text to audio for broadcasting. 12.2. Automated Message Preview. The system shall provide the ability to play back an automated broadcast notice prior to finalizing the automated transmission. 12.3. Automated Transmission. The system shall transmit the automated broadcast notice to mariners without impacting on-going distress communications. PHYSICAL CHARACTERISTICS The Radio/Console Control and Audio Route/Record/Replay Subsystem must be contained within 19-inch racks. Operator Consoles will be mounted on existing furniture wherever and whenever possible. Please provide information on equipment size, weight, power requirements, and heat load for a Radio/Console Control and Audio Route/Record/Replay Subsystem capable of supporting the number of required operator consoles and RFF base stations (see section 3). Please provide details on the impact of the number of operator consoles and base stations on the number of required 19-inch racks and related equipment. LOGISTICS SUPPORT In our experience, based on historical data, radio control systems should have a supportable life >= 10 years. The Coast Guard requests information on the OEM's product lifecycle support including the following: (1) description of how the company would maintain and sustain the product throughout a 10-year lifecycle (parts, components, firmware support, software support, compliance with information assurance standards, factory and/or depot support, and technical training) and (2) product reliability (i.e. Mean Time Between Failure [MTBF]) and maintainability (i.e. Mean Time To Repair [MTTR]). INSTALLATION SUPPORT The Coast Guard requests information on the capability to provide and install Radio Control System equipment at 32 operational sectors and 168 operational stations located in the continental United States, Hawaii, Puerto Rico, and Guam, and 2 test bed sites. Please provide a description of installation support experience that describes the ability to complete installations given a fixed or modified schedule (due to unplanned delays caused by Coast Guard operations). CAPABILITIES BRIEF If your company is interested in this RFI, please provide capabilities brief to include the Name of your company, address, phone, Point of Contact (POC) Name, email and phone, DUNS #, NAICS code, size of business, and any other pertinent information. ADDITIONAL SUBMISSION OF INFORMATION Interested parties are encouraged to submit a response which supports the company's claim that it presently has the products that provide the technology, performance, functionality and form fit required to satisfy the requirements or submit a response which identifies areas in the system requirements that are technologically unachievable. The Coast Guard's requirement may be refined based on knowledge gained from RFI submissions. Specifically, any interested parties are requested to provide the following information: 1. Positive statement of your interest in this procurement. 2. Description of product that will fulfill this requirement. 3. Do you offer a commercial product that meets the requirement as stated? 4. Do you offer a commercial product that could be modified to meet this requirement? 5. Are the items/services available on a commercial price list? If so, please provide applicable price list(s). 6. What is your average delivery lead time for this type of product? 7. Do you provide operation and maintenance manuals? System administration manuals? 8. Do you provide operator training? Maintenance training? System administration training? 9. A list of any proprietary data/components or embedded components for this product or data associated with this item. 10. A definitive statement on the willingness to enter into third party non-disclosures for the purpose of integrating the Radio Control System with standards-compliant transceivers and RFF alarm interfaces. 11. Existing technical documentation and brochures are welcome as attachments as well as product catalogs and price lists. 12. Information on prior Government and commercial purchases of the same type (pricing, performance, and customer satisfaction data). 13. Do you offer quantity or other discounts to your customers? 14. What are your warranty terms, if any? What is your standard warranty practice? Can you offer an innovative warranty approach that would cover the lag time from delivery to actual installation of the components? 15. Information for any additional charges for special packing and packaging and marking. Comments/questions/concerns are encouraged and should be sent in writing to the Contract Specialist, Katherine Kearney at Katherine.M.Kearney@uscg.mil. Upon receiving feedback, the Coast Guard will assess all input and its impact on the development of the final specifications. The NAICS Code for this solicitation is 334220 (marine radio communications equipment manufacturing). Contractors doing business with the Government are required to register in the System for Award Management (SAM) database before they can be awarded a contract. A template containing the information for registration can be found at: https://www.sam.gov/portal/public/SAM/ Responses must be no longer than fifteen pages in length. Technical documentation and brochures, if included, do not count in the fifteen page maximum. Submit your response by 2:00 PM EST on April 11, 2016 to the Contract Specialist, Katherine.M.Kearney@uscg.mil.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/1484e0bd5c40825a43a43b5b0ef4be97)
- Record
- SN04042967-W 20160310/160308234853-1484e0bd5c40825a43a43b5b0ef4be97 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |