MODIFICATION
58 -- EW Battalion
- Notice Date
- 5/29/2013
- Notice Type
- Modification/Amendment
- Contracting Office
- ACC-APG - Aberdeen Division B, HQ CECOM CONTRACTING CENTER, 6001 COMBAT DRIVE, ABERDEEN PROVING GROU, MD 21005-1846
- ZIP Code
- 21005-1846
- Solicitation Number
- MARKET-SURVEY-5449-1
- Response Due
- 6/24/2013
- Archive Date
- 7/28/2013
- Point of Contact
- Tineka C. Davis, 443-861-5439
- E-Mail Address
-
ACC-APG - Aberdeen Division B
(tineka.c.davis.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- FOR MORE INFORMATION PLEASE CONTACT: Technical Point of contact for this is Mark Claycomb, (443) 395-6993 mark.w.claycomb.civ@mail.mil The U.S. Army CECOM (also known as the US Government (USG) in the rest of this document) is issuing a Request for Information (RFI) including price and availability (P&A) to integrate and field Commercial Off-the-Shelf (COTS) Non-Developmental Item (NDI) Mobile Heavy Duty Tactical Electronic Warfare Systems. This FMS project will be led and fully managed by the USG with assistance from one company (called quote mark the contractor quote mark from here on) that would provide all services described below. Introduction This document describes the capabilities required by the USG for an Electronic Warfare Tactical Battalion. This requirement will fall under the Foreign Military Sales (FMS) program. The information herein shall serve as baseline for the systems capabilities, configuration and specification. The proposed systems shall include all efforts for installation, system integration, system testing, system operation, maintenance, logistic support, and training in country. If the requirements described below are unachievable or a cost driver, suitable alternatives shall be proposed. 1Requirements 2System Overview CECOM is issuing this document to request proposals from contractors to develop and field two (2) fully mobile Electronic Warfare tactical Companies (EW CO). Each company consists of: one (1) company EWOC (CO EWOC), six (6) mobile Communications Electronic Support (ES) systems, and two (2) mobile Communications Electronic Attack (EA) systems. Each company will be deployed in a three-platoon configuration. The following requirements represent the minimum specifications accepted by CECOM. Any additional features introduced by the contractor and exceeds these requirements will be considered as an advantage and will be taken into consideration in the evaluation process. These are minimum requirements and are by no means totally inclusive. They are intended to be a guide in setting the direction and expectations for the Electronic Warfare sub-systems. Supply, install, integrate and locally support two (2) EW Tactical companies each consists of: oOne (1) mobile Electronic Warfare Operations Center (EWOC) oSix (6) mobile V/UHF Communications Electronic Support (ES) systems. oTwo (2) mobile V/UHF Communications Electronic Attack (EA) systems. Secure broadband (HCLOS) communication between the CO EWOC and the forward ES and EA subsystems. Figure 1.1 Depicts the layout of one EW Company. This required EW system shall provide a state of the art solution for intercepting, monitoring, geo-locating and processing military communications signals. Mobile Heavy Duty Tactical Electronic Warfare System shall provide a state-of-the-art solution allowing the two companies to monitor, intercept, collect and locate radio communications and to selectively jam communications of enemy forces. Each company will operate independently from each other and will communicate to the Electronic Warfare Directorate (EWD) EWOC via the CO EWOC using an existed IP-based network. 3Electronic Warfare Operations Center (EWOC) The EWOC shall act as the tactical command and control center for the specific EW company system. The primary function of the EWOC shall be to maintain a central command post that is constantly in contact with higher headquarters. EWOC Equipments and operators are accommodated in a military shelter (S280) mounted on a 5-ton heavy-duty off-road truck or similar. The required functions of the EWOC are summarized as follows: Development and distribution of the battalion Common Operating Picture (COP) Support the development of the Electronic Order of Battle (EOB) Command and Control Communications network manager Collection manager Electronic Attack Manager Mission Planning Propagation analysis Jamming Effectiveness Analysis using receivers within the EWOC Coverage Analysis Multi-layered maps - showing deployment scenario and blue/red force status (Common Operating Picture) COP Line of Sight Path profile analysis Database Storage and Processing Analysis Tools and replay facility The EWOC shall consist of servers and workstation computers interconnected via a TCP/IP Local Area Network (LAN) to provide database processing, replay and analysis, situation display capabilities, HCLOS communications equipment, and IP interface to the existing IP network. The Collection Management and Electronic Attack scenarios shall be managed from the EWOC where the directions from the higher headquarters determine the tasking for the system. The reports and data produced by the system shall be delivered to the higher headquarters EWOC. The EWOC shall accommodate 4 positions: Mission Planning Manager Collection Manager Attack Manager Communications Manager Each workstation can perform any of the above positions. 3.1Functional Requirements 3.1.1Command and Control 3.1.1.1The EW company Electronic Warfare Operations Center (EWOC) shall serve as the mission planning, co-ordination with operational forces, tasking and deployment of ES and EA assets, communications management, preparation and transmission of operational orders and generation of tactical situation reports, and the analysis and Control Center for the EW company. 3.1.1.2The EWOC shall present the Electronic Order of Battle (EOB) for the EW Company. 3.1.1.3The EWOC shall operate at each deployed EW company headquarters 3.1.1.4The EWOC shall maintain the frequency plans for the radio networks. 3.1.1.5The EWOC shall be housed in a shelter mounted on a heavy-duty tactical vehicle with four ruggedized operator workstations that are software configurable to provide command post. 3.1.2Communications Management 3.1.2.1The communications manager function shall configure the communication radios, coordinate the frequencies of operation with the overall frequency management plan, configure the communication network and monitors the friendly forces links for transmission quality and operations protocol adherence. Use LOS (Line of Sight) tools for optimum deployment of company elements. 3.1.2.2The EWOC shall have propagation analysis tools for both mission planning and jamming effectiveness analysis. 3.1.2.3The EWOC shall be as one possible time reference unit for the rest of the company. 3.1.3Tasking 3.1.3.1The mission planning shall have the capability to translate high level battle orders tasking received from the HQ into company tasking. 3.1.3.2The tasks shall contain the following information: Relevant EW company element Task type Task priority Task schedule time. 3.1.3.3The tasks can be categorized into two types: Manual tasks: actions to be performed by the operator. Programmed tasks: initiated based on a schedule. 3.1.3.42.3.1.4 ES manual tasks contain: Tasks for General and Directed search operations. oFrequency band(s). oTime schedule. List of Signals of Interest SOIs. Actions to be performed by an operator when an SOI is observed: oAudio or IF recording oGeolocation 3.1.3.5EA manual tasks contain: Prioritized list of SOIs to attack oFrequency oBandwidth Jamming techniques to be used when SOI match is detected. oFrequency oAttack waveform oTransmit power 3.1.3.6ES automatic tasks contain: Tasks for General and Directed search operations. oFrequency Band(s) oTime schedule. List of SOIs Match criteria. For each SOI is an operator specified combination of SOI parameters: oFrequency oBandwidth oModulation oLine of Bearing Automatic follow-on actions performed when an SOI match is detected: oOperator tip for manual intervention oAudio or IF recording oGeolocation request 3.1.3.7EA programmed tasks contain: Prioritized list of SOIs to attack Match criteria for each SOI oFrequency oBandwidth Jamming technique to be used when an SOI match is detected. oFrequency oAttack waveform oTransmit power oBandwidth 3.1.3.8Collection/ES tasks can be originated from any of the four positions at the EWOC as well as the ESs, ES-NCSs, and EAs. 3.1.3.9Jamming/EA tasks can only be generated by the attack/EA manager at the EWOC. 3.1.4Collection/ES subsystems Management 3.1.4.1The collection manager function shall schedule tasking to the ES subsystems in the form of tasking messages which are derived from the mission planning functions and orders.. 3.1.4.2The collection manager function shall permit direction of the ES subsystems to perform certain missions such as general search, directed search, sector or area scan, location of specific targets according to a predefined schedule. 3.1.4.3The collection manager shall communicate with the ES Net Control Station (NCS) to relay the missions and tasking in the form of messages sent over communications net. 3.1.4.4Remote collection can be performed by EWOC operators through the HCLOS network into any ES. Remote collection includes listening to real-time conversations as well as recorded audio cuts. 3.1.5Jamming/EA subsystems Management 3.1.5.1The Electronic Attack (EA) manager function shall schedule jamming missions and target units in the enemy forces. 3.1.5.2The Electronic Attack manager function shall permit construction of a strategic plan prior to hostilities. 3.1.5.3During peacetime operations, the electronic attack manager shall be capable of processing information (from prior collected mission and stored in database using EWOC receivers) about the communications operations of the enemy forces such as the frequency of operation for each network, operating schedules, locations and movements, and modulation types. 3.1.5.4This information shall then be used to prepare a jamming strategy which includes items such as generation of frequency lists as a function of time of day, areas of operation, and number of emitters 3.1.5.5The electronic attack manager function shall issue tasking orders to the EA Jammer subsystem by means of the HCLOS communications links. 3.1.5.6The HCLOS communication shall be flexible to pass information through any other subsystem. 3.1.5.7The EA manager shall have the capability to measure jamming effectiveness. 3.1.5.8Propagation and coverage analysis tools shall also be available at the EA manager. 3.1.6Database storage and processing 3.1.6.1The database storage and processing function at the EWOC is a key element of the command and Control decision making, analysis and planning process. RDBMS Server software shall provide a relational database that can store any manually controlled synchronization function to include ES DF data collected by the ES subsystems, collection reports, Line of Bearings (LOB) to target data, tasking records, signal records, collection reports and location reports. 3.1.7Servers and Workstations 2.1.8.1Servers for collection, audio storage, database, backup (archives) shall be installed in the EWOC. 2.1.8.2Workstations within the shelters shall allow remote access to the subsystems, to conduct Supervisory and maintenance functions. 3.1.8Narrowband Monitoring and Collection 3.1.8.1A minimum of 12 NB (narrow band) receivers with monitoring antenna to cover the bandwidth 30-3000 MHz shall be provided. 3.1.8.2The specifications of those NB receivers shall match those at the ES. 4Communications Electronic Support (ES) The Communications Electronic Support (ES) mobile unit shall consist of one (1) V/UHF Communications Electronic Support (ES) sub-system operating against line of sight (V/UHF) integrated into a military shelter mountable on a tactical vehicle such as the expanded-capacity HMMWV under the same overall control, collection and database management software solution. A similar vehicle would be acceptable if the HMMWV is not available as long as it contains the same tactical performance capabilities. The US Government shall retain the right to GFE the vehicles if it is more economically feasible to them. Whichever vehicle is chosen must accommodate the system without the need for extra cargo capacity such as trailers. 4.1Functional Requirements The Communications Electronic Support (ES) system shall provide the capability to intercept, monitor, locate, analyze and report on tactical communications operating in the VHF and UHF bands in a battlefield environment. The ultimate objective of the ES is to develop the signals environment, geolocate emitters, identify the threat emitter networks, and collect signals intelligence and to disrupt those key networks during periods of hostility. 4.1.1General requirements 4.1.1.1All operation, control and configuration of equipment shall be performed locally in the shelter from the operator workstations. The option to add at least 4 additional workstations via an external LAN port on the wall of the shelter shall be provided with no hardware or software limitations. 4.1.1.2The ES MON/DF units shall operate in a semiautomatic mode, where the operator validates the decisions of the signal recognizer and FH net analysis processors and performs transcription of clear voice signals or in a manual mode by manually tuning the digital receivers, recording signals, preparing transcriptions, accepting tasking and generating reports. 4.1.1.3The Net Control Station (NCS) function shall be incorporated in each of the shelters and will perform the communications master as well as the geolocation, database management and collection management functions. 4.1.1.4A RDBMS processor shall be provided to store tasking, reports, signal parameters, Signal of Interest, Collection records, Audio/IF files (.wav for audio), Configurations files and mission parameters. Contractor format is acceptable for the reports. 4.1.1.5Quantity (2) two ruggedized operator workstations shall be provided in the shelter; each shall be able to operate all equipment supplied in the mobile unit. Ruggedized Operator laptops shall be dismountable and shall remotely control and operate all equipments in the shelter from a distance of at least 100 meters via a fiber cable or similar cable transmission line. 4.1.2Tasking 4.1.2.1The tasking system shall support the scheduling of automated tasks that integrates/combines different aspects and functions of the system into a single application. For example, schedule a signal recording if there is activity and then obtain a DF on the signal and perform decoding. 4.1.2.2Manual and automatic tasks can be configured locally by the ES operators in addition to tasking received from the EWOC or other ESs. Match criteria for SOIs can be configured and follow-on actions are triggered whenever a match is detected. 4.1.2.2.1ES operators shall be able to create collection tasks that include SOIs or frequency bands or both. 4.1.2.2.2The ES operator can control the allocation of resources (digital receivers and independent NB receivers) based on the task. 4.1.2.3The tasking system shall support configuration of the system to raise alerts to the operator that initiated the task when an automated task begins or ends. 4.1.2.4Task prioritization shall be supported. 4.1.3Wideband Direction Finding 4.1.3.1The system shall support geolocation using two or more stations using TCP/IP as a communications protocol. 4.1.3.2The results from 3.1.3.1 shall be automatically calculated and the emitter location plotted digitally on a map. 4.1.3.3The system shall obtain a DF if a specified signal exceeds a pre specified threshold. 4.1.3.4The DF subsystem shall support return of DF measurement after a specified number of readings or specified period of time. 4.1.3.5The system shall support detection and DF of frequency hopping signals with signal parameter classification, for example including dwell time, bandwidth, and hop rate. 4.1.3.6The geolocations derived from geolocation and DF single site location shall be stored in the database. 4.1.3.7The geolocations, LOB fixing and DF single site location shall be plotted using a mapping engine with ability to include the generated maps into a report. Contractor format is acceptable for the reports. DF results shall be displayed on screen in different ways including but not limited to: frequency vs. time vs. AoA (Angle of Arrival), polar view, direction histogram, recording and playback wideband direction scan results. 4.1.3.8The operator can span into or highlight a signal on the frequency spectrum display and request a DF on that signal. 4.1.4Geolocation support 4.1.4.1The ES sub-system shall include a positioning sub-system - GPS antenna mounted on the shelter with unobstructed view of the sky. 4.1.4.2The GPS receives signals from multiple GPS satellites & passes them to the GPS receiver. 4.1.4.3GPS receiver provides Network Time Protocol (NTP) to the network equipment for coordinated server & workstation time between sites. 4.1.4.4The alignment of the DF antenna with the True North shall be possible without intervention from the operator. In the case of failure of the automatic alignment function, the system shall allow a manual alignment. 4.1.4.5Real-time heading information shall be provided automatically to the DF processor. 4.1.4.6In case the automatic alignment process malfunctioned, the system shall allow for manual alignment. 4.1.4.7The ES sub-system shall support an integrated map application. 4.1.4.8The Geographic Information System (GIS) shall support standard mapping formats such as Shapefile (ESRI) format, GIF, JPG, JPEG, PDF, and TIFF. Map features, such as rivers, cities, roads, etc., can be added and removed from the displayed map. The system shall have the capability to allow the operator to add or remove layers to the map. 4.1.4.9Any GIS system that supports Google Earth format shall be considered a plus. 4.1.4.10The contractor shall provide, multi-layered, and maps to cover User country and its surrounding countries. 4.1.4.11The ES sub-system shall support networking of multiple DF systems for target location. 4.1.5Collection 4.1.5.1The collection system shall implement wideband monitoring with signal recognition. 4.1.5.2General Wideband search - the system shall be able to search for a specific type of signal within a specified frequency band(s), direction sector(s), or geographic area. 4.1.5.3Targeted Wideband search - the system shall be able to search for activity on pre-specified frequencies, signal direction, or geographic area. 4.1.5.4The collection system shall be configurable to automatically send alarms triggered by the wideband search, to any other collection element within the company. 4.1.5.5At least 32 NB digital receivers shall be embedded in the Wideband collection system to be used for NB collection. 4.1.5.6As part of the wideband search, the system shall have the capability to be automatically configured to log alarms, record signals, and allocation of NB resources, insert DF readings and perform decoding into the database. 4.1.5.7The collection system shall have the ability to define frequencies for signals not of interest and azimuths to be skipped in the wideband search. 4.1.5.8To insure correct signal recognition, the signal recognizer shall obtain DF AoA information in real-time during the interval that it is obtaining a LOB. 4.1.5.9The collection system shall provide manual control of the monitoring digital receivers as well as the NB independent receivers. 4.1.5.10The collection system shall have the ability to perform the following using monitoring digital receivers: frequency and band search (loaded from the tasking subsystem), recording and simultaneous playback of signals, Unicode transcription, intercept field data entry, live and recorded signal decoding, histogram and waterfall display of signals, DF measurement on a selected signals and store all intercept data in the database. 4.1.5.11The ES sub-systems shall have a minimum of 12 Narrowband receivers (30-3000MHz), which can work independently from the Wideband collection. In addition, the NB receivers can be controlled manually by the operator or allocated by the Wideband collection system. For example, during general search, if SOIs were found, one or more of the NB receivers can be allocated for AF recording for later processing or real-time monitoring. 4.1.5.12During NB monitoring, the operator shall have the capability to manually task the DF sub-system and the results stored in the database. 4.1.6Recording The recording sub-system shall support the following: 4.1.6.1Scheduled IF and AF recording. 4.1.6.2Scheduled IF and AF recording on the detection of active signals. 4.1.6.3SRI (signal related information) information shall be stored along with the associated audio cuts or IF signals, and should be retrieved during replay or when querying the database. 4.1.6.4During IF recording, the associated DF results must also be stored when requested for later analysis and processing. 4.1.7Digital data decoders/analyzers 4.1.7.1The Digital data decoders/analyzers shall include all functions required to analyze, decode, and process radio data communications in the VHF and UHF range, as described in the EWOC section 4.1.7.2The Digital data decoders/analyzers shall have the ability to automatically recognition radio data signals. 4.1.8Processing and Analysis The processing and analysis sub-system shall support the following: 4.1.8.1AF (audio frequency) and IF (intermediate frequency) decoding. 4.1.8.2Scheduled AF and IF decoding and saving the results in the database. 4.1.8.3AF and IF decoding from a recorded signal. 4.1.8.4Scheduled processing of frequency agile and burst emissions. 4.1.8.5Traffic processing tools for target signals. 4.1.8.6Offline signal processing tools including combining frequency hoppers. 4.1.8.7The Contractor shall, in response to this RFP, provide screen shots of the processing and analysis tools. 4.1.9Reporting 4.1.9.1DF LOBs and geolocations shall be plotted using a mapping engine with ability to generate a report that includes the map. 4.1.9.2During real-time and recorded NB monitoring, the operator shall have the ability to start a transcription tool which allows him to describe the conversation, fill out required fields, add details and remarks, and store it into the database. 4.1.9.3All SRI information shall be automatically loaded into the transcription software. 4.1.9.4All reports and transcriptions shall be electronically searchable (not using Windows query function but rather by using logical operators) by: Title Callsign Key word Word or phrase in the Contents using logical operators (AND, OR), wildcard, NOR) between words, and wildcarding. 4.1.10Database 4.1.10.1All intelligence data shall be saved in the local sub-system database as well as the central company EWOC database. 4.1.10.2The system shall allow for database synchronization of any new data between the EWOC and sub-systems, whenever requested. 4.1.10.3The central ES database server should be set up in a fail/safe cluster configuration. 4.1.10.4The system shall have a zeroizing function that allows the operator to erase all database information and any nonvolatile information within 3 minutes. 4.1.11Monitoring 4.1.11.1The ability to monitor the database server status shall be provided. 4.1.11.2The ability to monitor all systems and subsystems to insure proper operation and performance shall be provided. 4.1.11.3Built in Test (BIT) shall be provided for all systems and devices. This function shall include a diagnosis of the entire system and shall include troubleshooting features using such capabilities as decision trees, step by step directions and warnings to single out problems 4.1.11.4Whenever a sub-system fails, the monitoring mechanism shall trigger immediate alarms locally and at the EWOC. 4.1.12System Management and Configuration 4.1.12.1The ability to set user and group policies and permissions to system resources shall be supported. 4.1.12.2The ability to configure or manage any subsystem from a single configuration/management workstation shall be supported. 4.1.12.3Operator workstations shall contain a fully updated Microsoft Windows operating system. 4.2Mobile Wideband V/UHF DF and Monitoring Sub-system The Communications Electronic Support (ES) subsystem shall include a wideband DF subsystem that performs signal acquisition, detection and DF on all new energy alarms within the wideband instantaneous bandwidth, signal acquisition subsystem, automatic signal recognition, digital audio/IF recording, and collection digital receivers. Mobile wideband V/UHF DF and monitoring requirements are described as follow: 4.2.1V/UHF DF and Monitoring System requirements 4.2.1.1The mobile V/UHF wideband DF subsystem shall include automatic wideband signal acquisition subsystem, automatic signal recognition (for both Fixed Frequency and Frequency Hopping signals), digital audio/IF recording, and collection digital receivers with the ability to monitor one or more V/UHF single channel signal. 4.2.1.2N channel (at least 5) wideband V/UHF DF digital receiver/processor performing DF measurement of fixed frequency and frequency hopping signals and including a pneumatic mast, at least 30 ft, mounted DF antenna. 4.2.1.3It shall be possible to perform all operation, control and configuration of ES equipment fromt the CO EWOC. 4.2.1.4Operating frequency range: from 30 to 3000 MHz band 4.2.1.5Instantaneous bandwidth: at least 20 MHz. 4.2.1.6Scan rate: at least 10 GHz/sec. 4.2.1.7Coverage of 360 in azimuth. 4.2.1.8DF system accuracy of 2 RMS or better 4.2.1.9System sensitivity: (1 kHz IF bandwidth) of -120 dBm or better at the antenna ports. 4.2.1.10Selectable DF Bandwidth in steps from 6 KHz to 200 KHz or better. 4.2.1.11Hop Rate: 500 Hops/s. 4.2.1.12DF antenna shall intercept vertically polarized signals; interception of horizontally polarized signals will be a plus. 4.2.1.13Signal duration less than 1 msec. 4.2.2Mobile V/UHF Communications ES System Operation The Wide and V/UHF subsystem shall perform the following functions. 4.2.2.1Continuous frequency scanning, independent DF measurement and wideband acquisition mode to detect and simultaneously measures multiple signal parameters including DF for all detected emitters in an instantaneous bandwidth of at least 20 MHz scanning at a rate of at least 10 GHz/sec. 4.2.2.2Single frequency DF mode that permits manual tasking of the DF processor to provide continuous DF and monitoring on a single narrow band channel. 4.2.2.3Emitter Geolocation/Fix Determination that permits display of emitter locations derived from triangulation of LOBs from multiple wideband V/UHF subsystem on scanned (raster) paper maps in BMP format or Shapefile (ESRI) format. 4.2.3Detailed V/UHF Comms ES DF/MON antenna requirements The salient features of the required V/UHF Communications ES DF and MON antenna shall be as follows: 4.2.3.1V/UHF DF antenna including multiple bands splits across the operating spectrum. 4.2.3.2DF Antenna mounted on pneumatic mast (30 feet) on the vehicle within 30 minutes or better. 4.2.3.3The DF and monitor antennas shall be ruggedized for the tactical environment and can withstand wind speeds found in the user country environment. 4.2.3.4Lightning protection. 4.2.3.5All antennas and their connectors shall be sealed and waterproofed that meet MIL-STD-810G. 4.2.4Detailed V/UHF Comms ES acquisition subsystem requirements The salient features of the required V/UHF Communications ES acquisition subsystem shall be as follows: 4.2.4.1Frequency range, scan rate and instantaneous bandwidth of the acquisition sub-system shall be identical to V/UHF wideband DF subsystem. 4.2.4.2Wideband signal acquisition subsystem synchronized with/directed by the DF processor able to intercept fixed frequency and frequency hopping signals. 4.2.5Detailed V/UHF Comms ES signal recognition subsystem requirements The salient features of the required V/UHF Communications ES signal recognition subsystem shall be as follows: 4.2.5.1Automatic recognition of analog modulation Types (AM, FM, USB, LSB, CW,). 4.2.5.2Automatic recognition of digital modulation types (ASK, FSK 2 4 8, PSK 2 4 8 16, OQPSK, MSK, GMSK, FM-FSK, OFDM, and multi-carrier signals up to 64 levels or better). 4.2.5.3Automatic recognition of agile signal types (frequency hopping, spread spectrum, and burst signal). 4.2.5.4Number of Simultaneous Channels in Recognition is at least twenty four (24). 5Communications Electronic Attack (EA) The Communications Electronic Attack (EA) jamming techniques generator sub-systems shall be used in conjunction with state-of-the-art power amplification and directional and controllable antenna systems integrated into the Communications Electronic Attack (EA) mobile unit. 5.1Functional Requirements This section describes the functional requirements for the Communications (EA) that are common to both the V/UHF subsystems. 5.1.1General requirements 5.1.1.1The Communications Electronic Attack (EA) system shall provide the capability to electronically attack (jam) communication radios operating in the VHF and UHF bands in a battlefield environment. 5.1.1.2The equipment shall be housed in a military shelter mountable on an expanded-capacity HMMWV vehicle. 5.1.1.3All operation, control and configuration of equipment shall be performed locally and/or at the EWOC depending on the type of mission. 5.1.1.4The Communications Electronic Attack (EA) units shall operate in a semi-automatic mode with minimal operator interaction, in a semiautomatic mode where the operator validates the automatic decisions or in a manual mode by manually tuning the transmitters, choosing signals, accepting tasking and generating reports. 5.1.1.5Quantity (2) two ruggedized operator workstations shall be provided in the shelter; each shall be able to operate all equipment supplied in the mobile unit. Ruggedized Operator laptops should be dismountable and can remotely control and operate all equipments in the shelter from a reasonable distance via a coaxial or fiber cable. This configuration will provide survivability for the crew and protection from high power transmissions. 5.1.1.6Each EA shall be equipped with a positioning system (GPS). 5.1.1.7The EA subsystem should have four (4) Narrowband monitoring receivers and audio recording capabilities to support monitoring mission. The monitoring function shall have the same capabilities as those found in the ES. The intent is to give the EA operator extra monitoring capability when he is not jamming and to have jamming effectiveness capability without relying only on the ES or EWOC. 5.1.2Tasking 5.1.2.1The tasking system shall support the scheduling of automated tasks that integrates/combines different aspects and functions of the system into a single application. For example, schedule a jamming cycle. 5.1.2.2The tasking system shall support configuration of the system to raise alerts to the operator that initiated the task when an automated task begins or ends. 5.1.2.3Task prioritization shall be supported. 5.1.3System Management and Configuration 5.1.3.1The ability to set user and group policies and permissions to system resources shall be supported. 5.1.3.2The ability to configure or manage any subsystem from a single configuration / management module shall be supported. 5.1.3.3Operator workstations shall have a fully updated Microsoft Windows operating system. 5.1.4Monitoring 5.1.4.1Shall have the ability to monitor database server status. 5.1.4.2Shall have the ability to monitor all systems and subsystems to assure proper operation and performance. 5.1.4.3Shall have Built in Test (BIT) shall be as described in 3.1.11.3. 5.1.4.4The troubleshooting sub-system shall be a comprehensive process that enables the operator to test all sub-systems with detailed results. 5.1.4.5Whenever a sub-system fails, the monitoring mechanism shall trigger immediate alarms locally and at the EWOC. 5.1.4.6The operator shall perform pre-mission check-outs to verify that the EA jamming equipments are operating properly. 5.2Communications Electronic Attack (EA) sub-system This section describes the specific requirements for the sub-systems present in the Communications Electronic Attack (EA) unit. 5.2.1Communications Electronic Attack (EA) Techniques Generator Features Specific features of the Electronic Attack (EA) techniques generator subsystem shall include: 5.2.1.1EW jamming covering the tactical communications band of 30 to 3000 MHz. 5.2.1.2Ability to attack both conventional and frequency agile targets with minimum 500 hops per second in the V/UHF bands. 5.2.1.3The EA shall effectively disrupt frequency hoppers by using advanced sweeping techniques. 5.2.1.4V/UHF Instantaneous bandwidth: at least 20 MHz. 5.2.1.5Shall have the ability to attack 1 to 16 simultaneous targets in different frequency bands. 5.2.1.6Shall have the ability to prioritize targets, so that the correct amount of power is delivered. 5.2.1.7The system shall have a mechanism that assists the operator in determining the correct minimum power to be delivered and be effective against specific targets. The mechanism should factor in target parameters, environment and terrain conditions. 5.2.2Mobile Jamming Subsystem The mobile EA jamming subsystem shall have the following features: 5.2.2.1The configuration shall be mounted in a transportable shelter. 5.2.2.2Deployable and maneuverable in a tactical environment. The system shall be designed such that no more than two operators can do this. The design shall factor in the need for expediency and the fact that the operators may be uniformed in tactical uniforms. 5.2.2.3Tactical, antenna setup/tear down times should not exceed 60 minutes using 2 operators and shall feature log periodic transmit antennas with rotator that permits selection of direction from within the shelter. Antennas should support vertically polarized signals. Horizontally polarized antennas will be a plus. Storage of antennas while in the system is on the move shall minimize the need for storage hardware and containers. Instead, storage shall use available space within the shelter as much as feasible 5.2.2.4The antennas are preferred to be stowed on roof of shelter with a mechanism to secure it during transport. 5.2.2.5Attack VHF/UHF bands concurrently. 5.2.2.6Capable of attacking 16 simultaneous target frequencies not using a time division multiplexing method. 5.3EA Concept of Deployment 5.3.1EA Mission 5.3.1.1Prioritized Attack Frequency List - the mobile EA shall receive a list of fixed and hop frequencies currently in use - or known to be used by hostile forces from the mission planners at the EWOC 5.3.1.2Jammer Tasking - the jammer control workstation shall present the mobile EA operator with a jamming scenario editor that can be populated with information received from the EWOC. The operator shall then be able to choose to exercise any of barrage, mask (barrage inverse), or spot (point) jamming types. 5.3.1.3Start/Stop Jamming mission - the jammer control workstation shall present the mobile EA operator with a jammer status display that provides overall control of the jamming mission and allows the jammer to be started and stopped. 5.3.1.4As a precautious measure, a red light shall automatically turn on inside and outside the shelter whenever jamming is active. The light shall have a manual override. 5.3.2EA Attack Capability 5.3.2.1Look Through for a wideband (WB) system having an instantaneous bandwidth (IBW) of 20 MHz (called a quote mark stare quote mark ). This stare shall be moved anywhere about the RF spectrum from 30-3000 MHz (V/UHF). 5.3.2.2Detection - determines whether energy above a noise threshold is present in any frequency bin (12.5 KHz for V/UHF), and if it is, generates an alarm to the controlling unit. 5.3.2.3Look Up - implemented by transferring the target frequency information received by the ES or EWOC to the jamming scenario Interface. 5.3.2.4Lock Out Frequencies - the ability to accept at least 1,000 lockout frequencies. 5.3.2.5Frequency Masks - a contiguous range of frequencies that are defined to be in use by friendly forces. 5.3.2.6Barrage Range - frequency barrage ranges for jamming. 5.3.2.7500 W power amplifiers over the entire frequency spectrum 30 - 3000 MHz. 5.3.2.8The number of power amplifiers shall be at least three (3). Each PA has a power rating of at least 500 watts and covers portion of the frequency spectrum. 5.3.2.9The power of any amplifier shall be configurable by the operator. 5.3.2.10The type of jamming signals can be determined by the operator from a set of available signals. 5.3.2.11The system shall have a zeroizing capability to completely erase any information in the database and any other residing nonvolatile information within 3 minutes of initiation. 6Communications 6.1Intra-site communications Intra-site communications shall be accomplished using 10/100/1000 MB Ethernet Local Area Network (LAN). The computers and equipment within each shelter will communicate via TCP/IP sockets. 6.2Inter-site Communications 6.2.1HCLOS Communications System 6.2.1.1A HCLOS communications network shall be provided between the CO EWOC, ESs, and EAs. 6.2.1.2Harris RF-7800W or compatible HCLOS communications system shall be used to provide an easy to use and robust communications network and to be interoperable with existing EW elements using the same Harris radios. Features shall include: Voice and data communications. A telephone set or more shall be provided at each shelter for intra-site and inter-site VoIP connectivity. Management system to configure the radios and set up the communication links. Secure communications with the best possible commercial grade encryption capability. The encryption keys can be keyed-in into the system manually through a fill-gun, key-pad, or any other approved mechanism. Data rates that can accommodate tasking traffic, different functions, and any bandwidth consuming applications. Should support point-to-point (PTP) and point-to-multipoint (PTM) configurations. IP networking support. Frequency range above 3000 MHz. (if contractors selected a compatible radio with frequency range below 3000 MHz, a guaranteed interference cancellation mechanism should be in place). Compatible radios in the frequency range below 300 MHz are not acceptable. Mast mounted. If selected to be mounted on the ES shelter, should not affect the performance of the system. Support repeater configuration (radio relay). Contractors must understand that the terrain in the user country is diverse; as a result each company will have, in most cases a unique terrain. Radio links in one case will be approximately 70 Km, and in another case not more than 25 Km. when a PTP configuration is essential for one case, a PTM configuration may work for another case. 6.2.2HCLOS Radio Relay Towers 6.2.2.1We estimate that for some regions in the user country, the distances between EW elements (ES, EA, and EWOC) will be more than 30 Kms which makes it difficult to secure connectivity with each other, a fixed-site radio towers configuration must be proposed to provide extended range communications for a single company. 6.2.2.2Each HCLOS radio tower consists of two radios, two amplifiers, one Omni antenna, one directional antenna, and a relay unit. The user country will provide the towers and power for the radio equipment, Figure (5.1) depicts an example tower configuration. The configuration shall require 4 radios, i.e. 2 per tower. Fig (5.1): HCLOS Radio Tower Configuration (example) 6.2.1 Existing IP-based Network Infrastructure 6.2.1.1The EWOC shall have an IP interface to be directly connected to the existing IP network or through a router. 6.2.1.2The LAN at the CO EWOC and the LAN at the fixed site can be connected through a router. Traffic from/to both LANs can be routed between each other. 6.2.1.3The user country owns a wide coverage TETRA (Terrestrial Trunked Radio) communications network. It is preferable that all EW sub-systems be TETRA-enabled to supplement other communications when operating within coverage areas. This arrangement may require interference cancellation mechanism. 7vehicles and shelters. 7.1General 7.1.1All vehicles shall be capable of operating in tactical environments and similar in functionality and capability to non-armored 5-Ton military vehicles, HMMWVs, FMTVs, The vehicles shall have tires designed for tactical environments and provide ground clearances similar to the vehicles just mentioned. Commercial cargo trucks are not acceptable. All vehicle modifications shall be approved and certified by the manufacturer, and comply with the MIL-STD-1472G. The US Government reserves the right to GFE vehicles if it more economical to them. 7.1.2Electromagnetic shielding shall be provided to prevent outside signals from interfering with or corrupting the operation made by the sub-systems. Paint with RF shielding characteristics shall be utilized. 7.1.3Equipment and fixtures shall be ruggedized as necessary to reliably function in the physical environment defined for the sub-systems. The payload should not exceed 90% of the front and rear axles' capacity. The Central Gravity (CG) in three dimensions shall be within the safe margins set by the manufacturer 7.1.4Low-noise generators similar to Army tactical quiet generators that comply with the international standards shall be provided. 7.1.5The vehicles manufacturers' warranties shall be transferrable to the user country. 7.1.6Access to the equipment and/or vehicle components is required for preventive and regular maintenance without major disassembly of the sub-systems. 7.1.7Noise inside the vehicle shall meet OSHA standards and be controlled to provide an environment that allows safe operation as well as low fatigue for the personnel. 7.1.8Grounding system and attachment point to allow connection to earth ground when operating from external power sources or external antennas shall be provided. Single-point grounding mechanism is preferred in accordance with MIL-STD-188/124B. 7.1.9All vehicles shall have blackout driving light for movement under tactical light discipline conditions 7.2Electronic Warfare Operation Center (EWOC) 7.2.1The EWOC shall be housed in military shelter, preferred S280 with EMI protection, mountable on a heavy duty off-road 5-ton truck or similar tactical vehicle. If the system is compact enough to fit the components and 4 operators a smaller vehicle may be considered. 7.2.2The vehicle and shelter shall be new and in current production. 7.2.3The vehicle shall be off-road and customized to move on tactical terrain. 7.3Electronic Support (ES) and Electronic Attack (EA) 7.3.1Both, the ES and the EA shall be housed in a military shelter mountable on an expanded-capacity HMMWV or similar tactical vehicle. 7.3.2The vehicle and shelter shall be new and in current production. 7.4Support equipments 7.4.1All sub-systems shall have the following support equipments: Environmental Control Unit (ECU) Lightning protection and ground connections Safety equipment (fire extinguisher, first aid kit that meets MIL-STD-1472G,) Storage compartments that are not attached to equipment racks. Rain shields Rifle racks Color laser printers (1 per shelter) All equipments must be 220-240 VAC, 50 Hz. External power I/O panel allows for connection to an external power source. All panels shall have rain shields. All connectors shall have protective caps. Emergency lighting in case of main power loss Racks shall be accessible for maintenance with shock absorption for equipment protection Spare fuel jerrycans. Volt/Ampere/Hertz indicators shall be available inside the shelter. Conditioned power: UPS power supply that lasts at least 20 minutes of acceptable power for graceful system power down Desert tan color for both shelters and vehicles using water based CARC paint. Powder coating should be used as extensively as possible. German-type power sockets. Operator-driver intercom. Tie-down mechanism for seats during movement. Power distribution includes surge protection, a power panel, power monitoring, raceways, & outlets 8. Training 8.1System Operation Course 8.1.1Minimum duration: 5 weeks 8.1.2Minimum Number of students: 10 8.2System Maintenance Course 8.2.1Minimum duration: 3 weeks 8.2.2Minimum Number of students: 10 8.3System Engineering Course 8.3.1Minimum duration: 1 week 8.3.2Minimum Number of students: 10 8.4System Management Course 8.4.1Minimum duration: 1 week 8.4.2Minimum Number of students: 10 8.5All training shall be conducted at the contractor facilities. 8.6Training Objectives: 8.6.1Operate each of the sub-systems (EWOC, ES, and EA) 8.6.2Perform all preventive maintenance procedures 8.6.3Perform troubleshooting and repair procedures to the line replaceable unit (LRU) and shop replaceable units (SRU) level 8.6.4Understand the theoretical aspects of the system engineering and design 8.6.5Management and tasking of the system 9Documentation 9.1Operation and Maintenance Documentation Contractor shall provide standard operational and maintenance documentation, testing evaluation procedures for each of the mobile units. 9.2System and Equipment Documentation The Contractor shall make available the following system/equipment documentation 9.2.1System Operation Manual In addition to the one per system copy, upon final system acceptance by the Government, five (5) paper copies and five (5) electronic copies (CD/DVD), are to be submitted to the Government. All submitted copies shall include detailed system manuals describing the overall operational procedures and functionality of all components of the system and shall include copies of all commercial manuals. 9.2.2System Software Manual The Contractor is responsible for furnishing software manuals for all off-the-shelf, customized and special purpose software provided or developed for this project. Software manuals shall be provided as hardcopy and CD/DVD, with an unlimited license to reproduce copies. 9.2.3System Maintenance Manual The Contractor shall furnish complete and comprehensive installation and instruction manuals for all equipment and software in the system. These manuals shall provide concise information, including engineering drawings, troubleshooting diagrams, layout drawings, printed circuit board overlays, and test and alignment procedures, theory of operation, interconnection diagrams, and parts lists. Also included will be a list of maintenance and test equipment required for equipment maintenance prescribing make, model, description, manufacturer and alternatives. These manuals shall be suitable for rapid and efficient maintenance and repair of the equipment by a competent technician. At a minimum, 5 sets of installation, operation, and maintenance manuals shall be provided. 10Support 10.1Warranty 10.1.1System warranty shall be for at least (1) one year, from the date of field acceptance test in the user country, to cover 24 hours online or telephonic system support, labor, parts, including shipping costs. Warranty on all software shall be for at least (3) three years. 10.1.2All warranties start after the systems are delivered, tested, and accepted in The user country. 10.2Spare parts 10.2.1Required spare parts 10.2.1.1The proposal shall include initial spare parts package that is required for the sustainment of the project for the first year of operation after warranty. The cost of spare parts must be detailed in the cost proposal, and the total cost included in the system cost. 10.2.1.2A separate line shall be set aside to purchase spare parts. The contractor shall propose an initial set of spare parts. However, the actual spare parts purchase shall be decided during Critical Design Review (CDR). 10.2.1.3During warranty period, the contractor will replace faulty equipments/boards from his resources not from the spare parts package delivered with the project. 10.2.1.4The Contractor shall commit to provide spare parts, including third-party hardware and software, for 10 years after expiration of warranty when requested by the user country. This requires the contractor to plan how they will support the system considering possible obsolescence. 10.3Support after expiration of warranty Contractors shall submit prices for support per year after expiration of warranty. Support services shall include the entire system excluding cost of spare and replacement parts. 10.4Test Equipment The Contractor is responsible to include in the proposal any special test equipment required to maintain the installed system. This equipment shall be listed in the equipment detail and priced in the cost proposal. 10.5Soft copies of all system and operational installed software, firmware, and digital maps shall be delivered with the system to be used as backups. 11System Testing and Acceptance The shall include with their proposal a proposed Validation & Verification (V&V) mechanism as well as a system test procedure and a management plan for the execution of the system test procedure. The test plan shall include each major type of equipment and/or software as a separate test and shall include all RFP mandated features and functions of each type of equipment, a list of tests to be performed and how these tests will be administered. The contractor must provide all test equipment necessary to support these tests. The test plan shall be divided into four major testing milestones: Submission of the equipment Test Certificate to the Government. Factory Acceptance Test will be conducted at Contractor's location As an option, an Open-Air-Demonstration for one company shall be conducted at Yuma Proving grounds or a similar range that allows full spectrum test for the transmission, collection, and jamming. As an option, an Open-Air-Demonstration for one company shal be conducted at Yuma Proving grounds or a similar range that allows full spectrum test for the transmission, collection, and jamming. 12. Design review: The contractor shall prepare for the following meetings with the user country attendance at the contractor's facilities: 12.1. Kick off meeting. 12.2. Preliminary Design Review (PDR). 12.3. Critical Design Review (CDR) 12.4.Quarterly Review Meetings 12.5. Final Design Review. 12.6 Test Readiness Reviews 13General Conditions 13.1The contractors shall provide a requitrments compliance matrix showing how each requirement is being met and to what extent it is being met. Any requirement not being met completely shall be accompanied by a proposed solution. 13.2Complete datasheets and specifications for all equipments and sub-systems shall be provided along with the technical proposal. 13.3The EW Systems must be designed to be upgradeable and to adapt to new hardware and software over its lifetime the systems will use an open architecture that allows modularity and product improvement. 13.4Upon request, the contractor shall be ready to present a proposal that contains a detailed presentation on the offered system. This presentation, if requested, shall be delivered at a US Government location that will be announced with the request. The presentation may include any available demonstrable items (hardware or software) that will support the contractor's readiness to provide the system. 13.5The system shall be comprised of mature commercial-off-the-shelf hardware and software as much as possible. 13.6The contractor shall present a concept plan to inform the government how they would acquire, develop, test and demonstrate the system as required above. 13.7The contractors shall submit pricing as follows: Two Companies: 2 EWOCs, 12 ESs, 4 EAs, training, spares, documentation, etc. One Company: 1 EWOC, 6 ESs, 2 EAs, training, spares, documentation, etc. Detailed sub-system-level cost for initial and recurring systems as shown on Table 12.1. 14. Support Test Equipment 14.1 The Contractor is responsible to include in their proposal any special test equipment required to maintain the installed system. This equipment shall be listed in the equipment detail and priced in the cost proposal. 15. Provisos The Contractor shall be responsible to demonstrate that the system complies with any provisos. Contracting Office Address: 6001 Combat Drive, ACC-APG Sector C, Aberdeen Proving Ground, MD 21005 Place of Performance: N/A Point of Contact(s): Technical point of contact for this is Mark Claycomb, (443) 395-6993. EMAIL ADDRESSES: michiael.a.mitchell3.civ@mail.mil, mark.w.claycomb.civ@mail.mil Answering this Market Survey The responses to this market survey will be used for informational purposes only. The Government will not pay for any information received or costs incurred in preparing the response to the market survey. Therefore any cost associated with the market survey submission is solely at the interested vendor's expense. At this time the nature of the competition has not been determined. The Government may decide to do a full and open competition or set aside all or part of the procurement for small businesses, service-disabled veteran-owned small businesses or eligible socially and economically disadvantaged businesses that are certified by the SBA for participation in the SBA's 8(a) Program. The purpose of this market survey is to solicit statements of interest and capabilities from industry, including small businesses, service-disabled veteran-owned small businesses and 8(a) certified firms, All responses to this market survey must be received by 23 June 2013 at 4:00 PM CST.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/aa34a627069fd825eb911cb831569e19)
- Place of Performance
- Address: ACC-APG - Aberdeen Division B HQ CECOM CONTRACTING CENTER, 6001 COMBAT DRIVE ABERDEEN PROVING GROU MD
- Zip Code: 21005-1846
- Zip Code: 21005-1846
- Record
- SN03074391-W 20130531/130529235347-aa34a627069fd825eb911cb831569e19 (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 |