Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF FEBRUARY 16, 2005 FBO #1178
SOLICITATION NOTICE

58 -- FEMA National Radio System

Notice Date
2/14/2005
 
Notice Type
Solicitation Notice
 
NAICS
334290 — Other Communications Equipment Manufacturing
 
Contracting Office
P.O. Box 190022, North Charleston SC 29419-9022
 
ZIP Code
29419-9022
 
Solicitation Number
N65236-05-R-0530
 
Response Due
3/9/2005
 
Archive Date
4/8/2005
 
Point of Contact
Point of Contact - Dennis J Walp, Contract Specialist, 843-218-5978; Patricia Godwin, Contracting Officer, 843-218-5920
 
E-Mail Address
Contract Specialist
(dennis.walp@navy.mil)
 
Small Business Set-Aside
N/A
 
Description
The Space and Naval Warfare Systems Center Charleston (SSCC), Code 50 is tasked to procure, deliver and install high frequency (HF) radio communications equipment for the Federal Emergency Management Authority (FEMA). This contract shall provide systems meeting all requirements specified in the solicitation. The FEMA National Radio System (FNARS) is a HF radio network which provides essential emergency communications capabilities between federal, state, and local governments during emergencies or disasters. This system is regarded as a "first responder" communications mechanism which may be used to maintain reliable long and short range radio communications with affected disaster areas without dependence upon more susceptible commercial terrestrial and satellite telecommunications networks. The FNARS upgrade will utilize Automatic Link Establishment (ALE) capability in accordance with MIL-STD-188.141B (2G) and frequency shift keying (FSK) capability in accordance with MIL-STD-188-110B. MIL-STD-188-141C (3G) ALE capability will be installed upon third generation availability. The FNARS HF system will be utilized to transmit and receive secure and non-secure voice and data. Data shall include, but not limited to, e-mail, text messages and images. Data rate requirements are expected to be range between 9,600 and 19,200 bauds per second (BPS). A typical FNARS system will include operator consoles, HF radio transmission and reception equipment, RF matrices and antennas. A FEMA Ethernet switch and router will provide Network Control Center (NECOS), Federal Regional Center (FRC) and Regional Office (RO) system connectivity to the FEMA Wide Area Network (WAN) and will permit remote operation and control of these networked HF radio systems by NECOS, FRC or RO locations. Remote control and operation of HF radio systems will be accomplished using networked desktop or laptop computers. State Emergency Operations Center (EOC) HF radio equipment will not be connected to the FEMA WAN initially but will require local area network (LAN) remote operation and control. However, EOC radio equipment installations must be accomplished with the understanding that FEMA WAN connections may be required at some later date. Split-site HF systems may be required at some locations. In these cases, the transmitter and receiver will not be co-located. Therefore, for effective ALE operation, it will be necessary that the receiver and exciter be capable of remotely communicating with and controlling one another. In many cases a co-located transmitter and receiver (transceiver) will be required due to lack of funding or installation real estate for HF equipment and/or associated antennas. Ideally each FNARS installation will have a two (or multi-) radio configuration. One HF system would be utilized for voice communications and another HF system would be utilized for email and messaging communications. This configuration would permit the exchange of both voice and data without interruption to either communications medium. However, if a two radio installation is not possible due to either a lack of funding or real estate, an interface to preempt data traffic by higher priority voice traffic will be required. The HF radio equipment will include a Receiver/Exciter (for both combined and split systems), Automatic Link Establishment (ALE) and Link Quality Analysis (LQA), and will be adaptable to future Electronic Counter-Counter Measures (ECCM) waveforms. The systems will conform to Frequency Shift Keying (FSK), MIL-STD-188.110B and STANAG 5066. The equipment will include the ability to process 39 tone HF waveforms to ensure backward compatibility and current mission interoperability. The transmitter subsystems will be configured with 400W (or 500W), 1kW, and 4kW power amplification, depending upon station location, propagation requirements, network interoperability requirements, and special operations. The exact configuration will be determined by site survey, and network configuration. The 400/500W and 1kW systems must be contained in a single standard 72 inch high 19 inch wide rack but the 4kW systems may consist of two racks. At the Network Control Station (NECOS), FRC's and RO's, FNARS will use a modular, open system design to automatically operate and remotely control networked HF transmitter and receiver resources. This will include NECOS, FRC and RO systems at split site stations. To achieve maximum flexibility the FNARS will use commercially available standards based operations, control and communications software and a multi-tasking operating system. This will allow the station to operate "lights out" (unmanned) and to be economically controlled from a central location if necessary. It is a requirement that the HF radio equipment be capable of operating with KY-99A, KY-100, VP-116, DTD (AN/CYZ-10), and KIV-7 HSB communications security (COMSEC) equipment. The HF radio equipment manufacturer must also be capable of providing responsive technical support on site or via telephone on an "as needed" basis to either FEMA or SPAWAR Systems Center Charleston personnel. The radios will available for use based on 24 hours per day, 7 days per week. Technical support may be required at any time during the availability. The contract will be an Indefinite Delivery, Indefinite Quantity, Firm -Fixed -Price (FFP) type contract. Period of performance will be one base year with four one-year options. The approximate value of the contract will be $25,000,000.00. Place of delivery will be to Government sites as directed by individual delivery orders. SEE NOTE 22 MANDATORY PERFORMANCE SPECIFICATIONS, CONFIGURATIONS AND CONDITIONS · Automatic Link Establishment (ALE) with lowest acceptable maximum net capability of 14 channels minimum per net, with a minimum of 10 ALE nets available. · Minimum 200 channel memory capability. · Must be able to provide split site, full duplex capability (simultaneous transmit and receive ALE functionality at different locations). · Software programmable to allow for open architecture, easily upgradeable to new technologies. · Internal fault diagnostic/BITE tests with front panel and remote control display/indication of fault status. · Audible Fault/BIT alarms. · VSWR Fault indicator. · Able to be remotely controlled through an Internet based remote control system via a Serial or SNMP interface to the radio equipment. The radio system must be capable of being controlled from multiple control points. · Able to provide and utilize Link Quality Analysis (LQA) information. · Secure Voice capabilities. · Digital Voice capabilities. · Outputs of the following wattages, 400/500W, 1000W and 4000/5000W, PEP into a 50 ohm load. · Tuning range must be in the High Frequency Band (1.6 MHZ to 29.999999 MHZ) tunable in 10 HZ increments. · Single Sideband Operations, (SSB), including Upper and Lower Sidebands · Double Sideband (DSB) capability. · Two (2) Independent Sidebands (ISB). · Continuous Wave (CW) A1 modulation with A2 modulation desirable. · Amplitude Modulation (AM). · Push-to-Talk voice operation. · Capable of being interfaced to the following COMSEC equipments, KY-99A/100, DTD (AN/CYZ-10), VP-116 and KIV/7 HSB. · All radio software and firmware must be accessible through Windows 2000/Windows XP based operating software. · Capable of interfacing to STANAG 5066 compliant E-mail software such as Rockwell-Collins HF Messenger Version 3.3 (or higher) or equivalent software. · All radio software and firmware shall have a user-friendly Graphical User Interface (GUI) to initialize, monitor status and issue commands in both local and remote. Interface shall have visual and audible programmable alarms for equipment faults and degradation below limits. The GUI shall replicate all front panel functionality. · Transmit subsystem shall provide monitoring points for manual RF measurements accessible on the front or rear panels of the exciter or at some point before the power amp section. · Test points shall be provided for monitoring the audio signal path. ELECTRICAL/POWER · Front panel ON/OFF power switch. · External power for excitation/modulation sections, and RF amplifiers up to and including 1kW: 120/240 VAC 50/60 Hz + 10%, single phase. · External power for RF Amplifiers 4kW and above: 208, 240, 480 VAC + 10%, 3 phase MECHANICAL/PHYSICAL · Must be mountable in a 19 inch standard rack enclosure no greater than 24 inches deep and 72 inches high. · 400W (or 500W) and 1kW systems must be contained in a single rack. · 4kW systems are allowed to be contained in two racks. LOGISTICS · Warranty: Minimum 1 year, with 3-years preferred, full repair/replacement warranty. · Technical manuals provided to include at a minimum: o Theory of operation o Installation Control Drawings o Interface Control Specification o Schematics (CD media version is acceptable) o Operation manual o Maintenance manual o Logistics information o External wiring Pin Out tables · All equipment must be able to withstand an operational environment temperature range of -10 to +50 degrees C and up to 90 percent humidity. · Operational Availability (Ao) (Threshold) ³ .90 (Objective) ³ .95 · Mean Time Between Operational Mission Failure (MTBOMF) (Threshold) ³ 30,000 hours (Objective) ³ 40,000 hours · Mean Logistics Delay Time (MLDT) (Threshold) £ 120 hours (Objective) £ 24 hours · Mean Corrective Maintenance Time for Operational Mission Failures (MCMTOMF) (Threshold) £ 1 hour (Objective) £ .5 hour CERTIFICATIONS/QUALIFICATIONS · Commercial-Off-The Shelf (COTS) or Non-Developmental Items (NDI). Contractors and subcontractors shall incorporate COTS or NDI as components. · Solid state, no moving parts. · Automatic Link Establishment compliant to MIL-STD-188.141B (2G) and STANAG-5066. · Upgradeable to MIL-STD-188.141C (3G), when applicable. · Joint Interoperability Test Center (JITC) certification to MIL-STD-188.141B (2G) and STANAG-5066. · Should be able to accept Type I encryption for Voice and Data encryption must comply with NSA Certification and Standards. · Should be able to accept Type III encryption for Voice and Data encryption shall be in accordance with DHS Wireless Management Office (DHS/WMO) specifications and certified as compliant with applicable NIST Standards. · Contractor shall comply with the elements of FAR part 23, "Environment, Conservation, Occupational Safety and Drug-Free Workplace". · Must be compliant with the Buy American Act IAW FAR 25.1 requiring that only domestic end products be acquired for public use. REMOTE CONTROL INTERFACE REQUIREMENTS · General Requirement for remote control interface: The system shall be capable of being remotely controlled and managed from an external controller using either SNMP protocol over Transmission Control Protocol (TCP)/IP and User Datagram Protocol (UDP)/IP or a serial interface to the radio equipment. The external controller will be hosted on a government approved personal computer or server hardware platform and operating system. The remote control interface to the radio shall be available regardless of any front panel or vendor developed control capability, which may otherwise exist. The remote control interface capability must be able to duplicate any functions that can be otherwise be provided via the front panel or by the vendor developed control interface with no degradation of performance or capability. · Remote Control Interface: The contractor shall identify the specific remote control interface the device or system is capable of and define the control protocol that is being used (i.e. SNMP, Serial). The contractor shall provide documentation on any existing vendor developed HMI/GUI for control operations. The contractor shall identify whether the device, system or control software can provide higher level reporting to an enterprise management system, of the device or system configuration, status and/or faults. Simple Network Management Protocol (SNMP): If a system or device is capable of a SNMP remote control interface, the managed device or system configuration parameters that are accessible are specified by an interface protocol, namely the Management Information Base (MIB). MIB parameters are designated Object IDs (OIDs) in a tree structure and defines how remote users can either set or get the values of these OIDs. Additionally, the MIB is commented to specify the values possible for each OID and how these OIDs are used to either monitor or control the managed device. The contractor shall provide the actual MIB and/or an Interface Control Document (ICD) that contains the complete read/write Management Information Base (MIB) parameters for that SNMP interface. · Serial Military Standard Interface: If a system or device is capable of a Serial (i.e. RS-232, RS-422 etc) remote control interface, the contractor shall provide the interface protocol and interface control standard document which outlines the specific command sets, strings and/or events which can be set or provided via the serial control interface. These command sets/strings shall be documented in a table that outlines the specific command set, values and description of what the command set does. OTHER CONDITIONS/REQUIREMENTS · Contractor must provide Ao and cost data for maintaining the radio system over a 10 year-period. Assume that minimum Ao = 90 and maximum Ao = 100 and that the equipment will be available for use 24/7 365 days a year. · Contractor must provide a recommended spare part list and cost for each transmitter system listed based upon submitted Ao. · Contractor will provide any licensing costs for vendor developed control applications on a per user basis. · Contractor will be required to provide updated control information (SNMP MIB or Serial ICD) based on any hardware, firmware or software changes which impact the control interface or a statement of non impact. Contractor will be required to disclose their common business practice of how they respond technically to service requests from their clients on a 24hour, 7day a week basis and provide depth of their service capability. Projected solicitation release date is 23 February 2005. NOTE: THIS NOTICE WAS NOT POSTED TO WWW.FEDBIZOPPS.GOV ON THE DATE INDICATED IN THE NOTICE ITSELF (14-FEB-2005); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
 
Web Link
Click on this link to access the SPAWAR Solicitation Page
(http://www.eps.gov/spg/DON/SPAWAR/SPAWARSYSCEN_Charleston/N65236-05-R-0530/listing.html)
 
Record
SN00750777-F 20050216/050214211917 (fbodaily.com)
 
Source
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.