Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF APRIL 06, 2014 FBO #4516
MODIFICATION

58 -- Electronic Warfare Battalion Phase 2 (EWB2) for a Coalition Partner Country (CPC).

Notice Date

4/4/2014
 

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-5583-1
 

Response Due

4/18/2014
 

Archive Date

6/3/2014
 

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: PCO Primary Toni Quiroz Email: Toni.Quiroz@us.army.mil, PCO Secondary Mark Claycomb mark.w.claycomb.civ@mail.mil AMENDMENT #2: There is additional information regarding this survey from the USG concerning the RFI that all interested vendors should inquire about. Please contact the POC's listed above to get this information. Also please note that the response date has been extended from 4/11/2014-4/18/2014 AMENDMENT #1: Please read the below note that was added to this survey on 3/26/2014: Government Furnished Equipment (GFE). The US government shall furnish as GFE all required vehicles, shelters, environmental control units, trailers and applicable towers for antennas, power generators, racks, non-system specific cables, communications radios, non-system specific power supplies, grounding kits, uninterruptible power supplies, any non-system specific hardware, storage units, operator work station furniture, connectors, and any required non-system specific hardware. The intent is to accept system hardware and software (ES, EA and EWOC) provided by vendors and integrate that equipment with the GFE to complete the system. The U.S. Army RDECOM (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 provide the equipment necessary to develop two (2) Electronic Warfare Companies (EW) to be incorporated as part of an Electronic Warfare Battalion Phase 2 (EWB2) for a Coalition Partner Country (CPC). This project will fall under a Foreign Military Sales (FMS) case. The EW company systems shall be developed using Commercial-Off-The-Shelf (COTS) Non-Developmental Item (NDI) hardware and software. This FMS project will be led and fully managed by the USG. III.Introduction a.This document describes the services required by the USG to deliver two (2) Electronic Warfare Operations Centers (EWOC), six (6) Electronic Support (ES) systems, and four (4) Electronic Attack (EA) sub-systems. The requirement shall include all efforts from a contractor to develop a system, support the integration effort, and support the USG on the sections described below. Specific services required by the US Army CERDEC from the contractor are as follows: IV.Special Instructions a.This RFI encompasses the work to build a complete system consisting of EWOC, ES, and EA. The technical requirements listed in this RFI do not include certain specific technical specifications. They are being omitted because of sensitivity concerns. These shall be supplied to interested vendors via separate message. b.Interested vendors are welcome to submit a proposal to develop all or part of the systems. That is, a vendor may choose to only provide the EWOC, ES, or EA. c.If a vendor chooses to provide only a sub-system they are still required to ensure that the sub-system is interoperable with the rest of the system. d.The RFI contains sections below that apply to the entire system as well as each sub-system. V.Program Requirements for Entire System a.Provide an overall Program Manager whom will interface with the USG. b.Provide to the USG a proposed Integrated Master Schedule (IMS). c.Provide to the USG a requirements compliance matrix. d.Provide an overall system size, weight, and power (SWAP). e.Provide cost of the entire effort. f.Provide a risk assessment matrix. g.Provide the assumptions made to develop the system. h.Comply with appropriate provisos. The USG shall provide these to all interested vendors via separate message. i.The contractor shall develop the system in accordance with Appendix A. j.The contractor shall provide the system components to the USG whom will integrate them into a platform consisting of a vehicle, shelter, communications system, power system, trailer (if any), ECU, and antenna masts. Integration will include installation into rack systems and operator workstations k.The contractor shall conduct a Factory Acceptance Test (FAT) at their location l.The contractor shall provide engineering support on the following events: i.Participate in the major milestones of the EWB ii.Overall integration in the USG facility iii.Demonstration and Tests CONUS iv.Demonstration OCONUS v.Five day site survey in OCONUS m.Provide operator and maintainer training as well as the training package in OCONUS. This training shall be incorporated into a USG designed overall system training package. n.Provide operator and maintainer user manuals o.Provide system software copies and licenses as a part of the system p.Provide with the system a 12 month warranty on the system hardware and a 36 month system software warranty which shall start after the conclusion of the field demonstration OCONUS q.Provide an initial/recommended set of system spares VI.Program Management a.The program manager shall be PMP certified. b.The program manager shall be the single company point of contact. The program manager shall address all program issues. VII.Integrated Master Schedule The IMS is the single integrated schedule that identifies the dates of all work to be completed by the Contractor. Other schedules referred to or developed during this contract shall not conflict with the IMS. This IMS shall become part of the overall USG IMS. The IMS shall be developed using Microsoft Project. The Contractor shall develop an IMS for the ES systems that contains at a minimum the following milestones and information: a.Materiel purchases b.System integration support c.Post Award Meeting d.Design Reviews (PDR, CDR) e.Program Management Reviews (PMR) f.Periodic Project In-progress Reviews g.Site survey to CPC h.Test Readiness Reviews (TRR) i.Acceptance Test j.Functional Demonstration k.Delivery of system to USG VIII.Requirements Compliance Matrix The requirements compliance matrix shall include all listed requirements. At a minimum the matrix will have the following columns: Requirements, Meet (Y/N), Remarks (mitigation plan). In the remarks column the contractor shall list reason why the requirement was partially or not met. The contractor will also include their mitigation plan for the failed requirement. The contractor shall add at their discretion any implied requirements. IX.Size, Weight, and Power a.The proposed system shall fit within two racks measuring 19 inches wide by 43.75 inches tall by 30 inches deep. b.The contractor shall provide a power budget for the entire system. This information is needed for the USG to choose the correct power system. c.The contractor shall provide weight and volume for the entire system. X.USG Provisos a.This system will have to be approved for sale by the appropriate US agency. This agency will provide some detailing of what technologies may not be approved for sale. This information will be provided to interested vendors at a later date via separate message. b.The contractor shall demonstrate compliance with any provisos. XI.Factory Acceptance Test a.Prior to delivery to the USG, FAT shall be conducted at the contractor location to demonstrate compliance with the technical requirements. This FAT may be conducted in the absence of the system being fully integrated into a platform. b.After equipment delivery to the USG, the contractor shall support a 30 day USG FAT at Aberdeen Proving Ground. The purpose of this FAT is to ensure that the entire system and all sub-systems work together properly before customer FAT. c.The contractor shall support a 2 week customer FAT at Aberdeen Proving Ground. The purpose of this FAT is to demonstrate to the customer that the entire system and all sub-systems work together properly before CONUS field demonstration. XII.Field Demonstrations a.The contractor shall support a three day USG Field Demonstration at Aberdeen Proving Ground. This demonstration shall not involve the end user. b.The contractor shall support a five day USG Field Demonstration OCONUS. This demonstration shall involve the end user. XIII.Training a.The Contractor shall provide input into operator and maintainer courses. The contractor shall recommend a training course based on the following conditions: i.The students will include foreign officer personnel with predominantly engineering degrees. ii.The course will be taught in English. Most students will only have a basic understanding of the English language. iii.Based on the previously mentioned criteria the contractor shall provide an estimate on how long sub-system training should take. b.The training shall consist of predominately hands on training and minimal theoretical training. c.Maintainer training shall be at Level I and Level II. The training shall include running of the BIT and replacement of LRUs of required test equipment. d.The trainers shall be fully knowledgeable in the operation and maintenance of the system. XIV.Documentation a.The contractor shall make available the following system/equipment documentation: i.System Operation Manual ii.System Software Manual iii.System Maintenance Manual b.The contractor shall provide final test plans for the internal contractor FAT 60 days prior to the event. c.The contractor shall provide final test reports no later than 15 days after conclusion of internal contractor FAT. d.The contractor shall provide, as applicable, e.The contractor shall provide the system Interconnect Diagram (ICD). XV.Software a.Soft copies of all system and operational installed software, and firmware shall be delivered with the system to be used as backups. b.Software input/output format...(contractor would have to determine) XVI.Warranty a.The contractor shall provide in the final cost, a 12 month system warranty for all components and sub-components effective from the date of system acceptance in-country. If individual system components have longer warranty periods the contractor shall state so. The contractor shall provide a complete written warranty stating instructions on making claims, wear and tear clause, turn-around time on repaired items, and cost responsibilities. The warranty shall include crate and package, cost of transportation of equipment to and from OCONUS. b.The contractor shall propose, as an option, technical support service either by in-country representative or remotely by e-mail, phone or internet help desk for a minimum of 12 months, 24 hours, 7 days a week. c.All warranties start after the systems are delivered, tested, and accepted in the user country. d.Cost shall include software updates and licenses for 36-months after acceptance of system in OCONUS. XVII.Spares a.The contractor shall propose an initial set of spare parts. However, the actual spare parts purchased shall be decided during Critical Design Review (CDR). b.The proposal shall include a proposed spare parts list and cost that would be required for the sustainment of the system for 12 months after the initial 12 month warranty expires. c.The 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. Appendix A 1.Electronic Warfare Operations Center (EWOC) 1.1.Introduction 1.1.1.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 Equipment and operators are accommodated in a military shelter (S280 with tunnel mounted generator) mounted on a Navistar unarmored 7000 4x4 series MV vehicle. 1.1.2.The required functions of the EWOC are summarized as follows: a.Development and distribution of the battalion Common Operating Picture (COP) b.Support the development of the Electronic Order of Battle (EOB) c.Command and Control d.Communications network manager e.Collection manager f.Electronic Attack Manager g.Mission Planning h.Propagation analysis i.Jamming Effectiveness Analysis using receivers within the EWOC Coverage Analysis j.Multi-layered maps showing deployment scenario and blue/red force status (Common Operating Picture) COP k.Line of Sight Path profile analysis l.Database Storage and Processing m.Analysis Tools and replay facility 1.1.1.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 1.1.2.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. 1.1.3.The EWOC shall accommodate 4 positions: Mission Planning Manager; Collection Manager; Attack Manager; Communications Manager. Each workstation can perform any of the above positions. 1.2.Functional Requirements 1.2.1.The EW company EWOC shall serve as the mission planning, coordination 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. 1.2.2.The EWOC shall present the Electronic Order of Battle (EOB) for the EW Company. 1.2.3.The EWOC shall operate at each deployed EW company headquarters. 1.2.4.The EWOC shall maintain the frequency plans for the radio networks. 1.2.5.The 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. 1.3.Tasking 1.3.1.The mission planning shall have the capability to translate high level battle orders tasking received from the HQ into company tasking. 1.3.2.An EWOC shall serve as the mission planning, co-ordination with operational forces, tasking and deployment of ES assets. The tasks shall contain the following information: a.Relevant EW Company Element b.Task Type c.Task Priority d.Task Schedule Time 1.3.3.The tasks can be categorized into two types: a.Manual Tasks - actions to be performed by the operator. b.Programmed Tasks - initiated based on a schedule. 1.3.4.ES Manual Tasks 1.3.4.1.ES manual tasks contain tasks for general and directed search operations. a.Frequency Band(s) b.Time Schedule 1.3.4.2.ES manual tasks contain a list of Signals of Interest (SOIs). 1.3.4.3.Actions to be performed by an operator when an SOI is observed: a.Audio or IF recording b.Geolocation 1.3.5.EA Manual Tasks 1.3.5.1.EA manual tasks contain a prioritized list of SOIs to attack. a.Frequency b.Bandwidth 1.3.5.2.EA manual tasks contain jamming techniques to be used when SOI match is detected. a.Frequency b.Attack Waveform c.Transmit Power 1.3.6.ES Programmed Tasks 1.3.6.1.ES programmed tasks contain tasks for general and directed search operations. a.Frequency Band(s) b.Time Schedule 1.3.6.2.ES programmed tasks contain a list of SOIs. 1.3.6.3.ES programmed tasks contain match criteria. For each SOI there is an operator specified combination of SOI parameters. a.Frequency b.Bandwidth c.Modulation d.Line of Bearing 1.3.6.4.ES programmed tasks contain automatic follow-on actions performed when an SOI match is detected. a.Operator tip for manual intervention b.Audio or IF recording c.Geolocation request 1.3.7.EA Programmed Tasks 1.3.7.1.EA programmed tasks contain prioritized list of SOIs to attack. 1.3.7.2.EA programmed tasks contain match criteria for each SOI. a.Frequency b.Bandwidth 1.3.7.3.EA programmed tasks contain a jamming technique to be used when an SOI match is detected. a.Frequency b.Attack Waveform c.Transmit Power d.Bandwidth 1.3.7.4.Collection/ES tasks can be originated from any of the four positions at the EWOC as well as the ESs, ES-NCSs and EAs. 1.3.7.5.Jamming/EA tasks can only be generated by the attack/EA manager at the EWOC. 1.4.Communication Management 1.4.1.The 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. 1.4.2.The EWOC shall have propagation analysis tools for both mission planning and jamming effectiveness analysis. 1.4.3.The EWOC shall be as one possible time reference unit for the rest of the company 1.5.Collection/ES Subsystems Management 1.5.1.The 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. 1.5.2.The 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. 1.5.3.The 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. 1.5.4.Remote 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. 1.6.Jamming/EA Subsystems Management 1.6.1.The EA manager function shall schedule jamming missions and target units in the enemy forces. 1.6.2.The Electronic Attack manager function shall permit construction of a strategic plan prior to hostilities. 1.6.3.During peacetime operations, the electronic attack manager shall be capable of processing information 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. 1.6.4.The electronic attack manager shall be capable of processing information (from prior collected mission and stored in database using EWOC database) 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. This information shall then be used to prepare a jamming strategy which includes items such as generation of frequency lists as a function of time, day, areas of operation, and number of emitters. 1.6.5.The electronic attack manager function shall issue tasking orders to the EA Jammer subsystem by means of the HCLOS communications links. 1.6.6.The HCLOS communication shall be flexible to pass information through any other subsystem 1.6.7.The EA manager shall have the capability to measure jamming effectiveness. 1.6.8.Propagation and coverage analysis tools shall also be available at the EA manager. 1.7.Database Storage and Processing 1.7.1.The 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. 1.8.Servers & Workstations 1.8.1.Servers for collection, audio storage, database, backup (archives) shall be installed in the EWOC. 1.8.2.Workstations within the shelters shall allow remote access to the subsystems, to conduct Supervisory and maintenance functions. 1.9.Collection Manager 1.9.1.A collection manager function shall schedule tasking to the ES subsystems from the EWOC in the form of tasking messages which are derived from the mission planning functions and orders. Note: Although the EWOC functions and development is not part of the system requirements, the ES shall be able to receive the tasking data from the EWOC via High Capacity Line of Sight (HCLOS) communications. 1.9.2.The 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. 1.9.3.The collection manager shall communicate with the ES Net Control Station (NCS) to relay the missions and tasking in the form of messages sent over through a communications network. 1.9.4.Remote 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. 1.9.5.Collection/ES tasks can be originated from the EWOC as well as the ESs or ES-NCSs. 1.9.6.The Relational Database Management System (RDBMS) Server software at the EWOC 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 2.Electronic Support (ES) 2.1.Introduction 2.1.1.The 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, collect signals intelligence and to disrupt those key networks during periods of hostility. 2.1.2.The ES mobile unit shall consist of one (1) V/UHF ES sub-system operating against line of sight (V/UHF) integrated into a military shelter (S280 with tunnel mounted generator) mounted on a Navistar unarmored 7000 4x4 series MV vehicle. 2.2.Functional Requirements 2.2.1.All 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. 2.2.2.The ES monitor/DF units shall operate in a semiautomatic mode, where the operator validates the decisions of the signal recognizer and FH net analysis processors to perform 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. 2.2.3.The 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. 2.2.4.A Relational Database Management System (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. 2.2.5.Quantity (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 equipment in the shelter from a distance of at least 100 meters via a fiber cable or similar transmission line cable. 2.3.Tasking 2.3.1.The tasking system shall support the scheduling of programmed 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. 2.3.2.Manual and programmed 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. 2.3.3.ES operators shall be able to create collection tasks that include SOIs, frequency bands or both. 2.3.4.The ES operator can control the allocation of resources (digital receivers and independent NB receivers) based on the task. 2.3.5.The 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. 2.3.6.Task prioritization shall be supported. 2.4.Wideband Direction Finding 2.4.1.The system shall support geolocation using two or more stations using TCP/IP as the communications protocol. 2.4.2.The geolocation from 3.5.a shall be automatically calculated and the emitter location plotted digitally on a map. 2.4.3.The system shall obtain a DF if a specified signal exceeds a pre-specified threshold. 2.4.4.The DF subsystem shall support return of DF measurement by a specified number of readings or specified period of time. 2.4.5.The system shall support detection and DF of frequency hopping signals with signal parameter classification, for example including dwell time, bandwidth, and hop rate. 2.4.6.The geolocations derived from the Lat-long and DF single site location shall be stored in the database. 2.4.7.The 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. 2.4.8.The operator can span into or highlight a signal on the frequency spectrum display and request a DF on that signal. 2.5.Geolocation Support 2.5.1.The ES sub-system shall include a positioning sub-system - GPS antenna mounted on the shelter with unobstructed view of the sky. 2.5.2.The GPS receives signals from multiple GPS satellites & passes them to the GPS receiver. 2.5.3.GPS receiver provides Network Time Protocol (NTP) to the network equipment for coordinated server & workstation time between sites. 2.5.4.The 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. 2.5.5.Real-time heading information shall be provided automatically to the DF processor. 2.5.6.In case of a malfunction of the automatic alignment process, the system shall allow manual alignment. 2.5.7.The ES sub-system shall support an integrated map application. 2.5.8.The 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. 2.5.9.Any GIS system that supports Google Earth format shall be considered a plus 2.5.10.The contractor shall provide, multi-layered and maps to cover user country and its surrounding countries. 2.5.11.The ES sub-system shall support networking of multiple DF systems for target location. 2.6.Collection 2.6.1.The collection system shall implement wideband monitoring with signal recognition. 2.6.2.General 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. 2.6.3.Targeted Wideband search - the system shall be able to search for activity on pre-specified frequencies, signal direction or geographic area. 2.6.4.The collection system shall be configurable to automatically send alarms triggered by the wideband search, to any other collection element within the company. 2.6.5.At least 32 NB digital receivers shall be embedded in the Wideband collection system to be used for NB collection. 2.6.6.As 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. 2.6.7.The collection system shall have the ability to define frequencies for signals not of interest and azimuths to be skipped in the wideband search. 2.6.8.To insure correct signal recognition, the signal recognizer shall obtain DF AoA information in real-time during the interval that it is obtaining a LOB. 2.6.9.The collection system shall provide manual control of the monitoring digital receivers as well as the NB independent receivers. 2.6.10.The 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. 2.6.11.The ES sub-systems shall have a minimum of 12 Narrowband receivers ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)), 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. 2.6.12.During NB monitoring, the operator shall have the capability to manually task the DF sub-system and the results stored in the database. 2.7.Recording 2.7.1.The recording subsystem shall support the following: a.Scheduled IF and AF recording. b.Scheduled IF and AF recording on the detection of active signals. c.SRI (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. 2.8.Digital Data Analyzers 2.8.1.The Digital data analyzers shall include all functions required to analyze and process radio data communications in the VHF and UHF range. 2.8.2.The Digital data analyzers shall have the ability to automatically recognize` radio data signals. 2.9.Processing & Analysis 2.9.1.The processing and analysis sub-system shall support the following: a.AF (audio frequency) and IF (intermediate frequency) analyzing. b.Scheduled AF and IF analyzing and saving the results in the database. c.AF and IF analyzing from a recorded signal. d.Scheduled processing of frequency agile and burst emissions. e.Traffic processing tools for target signals. f.Offline signal processing tools including combining frequency hoppers. g.The Contractor shall, in response to this RFP, provide screen shots of the processing and analysis tools. 2.10. Reporting 2.10.1.DF LOBs and geolocations shall be plotted using a mapping engine with ability to generate a report that includes the map. 2.10.2.During 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. 2.10.3.All SRI information shall be automatically loaded into the transcription software. 2.10.4.All reports and transcriptions shall be electronically searchable (not using Windows query function but rather by using logical operators) by: a.Title b.Call Sign c.Key Word d.Word or phrase in the Contents using logical operators (AND, OR), wildcard, NOR) between words, and wildcarding 2.11. Database 2.11.1.All intelligence data shall be saved in the local sub-system database as well as the central company EWOC database. 2.11.2.The system shall allow for database synchronization of any new data between the EWOC and sub-systems, whenever requested. 2.11.3.The central ES database server should be set up in a fail/safe cluster configuration. 2.11.4.The system shall have a zeroizing function that allows the operator to erase all database information and any nonvolatile information within 3 minutes. 2.12. Monitoring 2.12.1.The ability to monitor the database server status shall be provided. 2.12.2.The ability to monitor all systems and subsystems to insure proper operation and performance shall be provided. 2.12.3.Built 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. 2.12.4.Whenever a sub-system fails, the monitoring mechanism shall trigger immediate alarms locally and at the EWOC. 2.13. System Management & Configuration 2.13.1.The ability to set user and group policies and permissions to system resources shall be supported. 2.13.2.The ability to configure or manage any subsystem from a single configuration/management workstation shall be supported. 2.13.3.Operator workstations shall contain a fully updated Microsoft Windows operating system. 2.14. Mobile Wideband V/UHF DF & Monitoring Subsystem 2.14.1.The Communications 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, signal recognition, digital audio/IF recording and collection digital receivers. 2.14.2.V/UHF DF & Monitoring System Requirements shall include: a.The mobile V/UHF wideband DF subsystem shall include wideband signal acquisition subsystem, 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. b.N 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. c.It shall be possible to perform all operation, control and configuration of ES equipment from the CO EWOC. d.Operating Frequency Range: from 30 to 3000 MHz band. e.Instantaneous Bandwidth: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). f.Scan Rate: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). g.Coverage of 360 in azimuth. h.DF System Accuracy: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) i.System Sensitivity: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) j.Selectable DF Bandwidth: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) k.Hop Rate: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) l.DF antenna shall intercept vertically polarized signals; interception of horizontally polarized signals will be a plus. m.Signal Duration: ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) 2.15. Mobile V/UHF Communications ES System Operation 2.15.1.Wide and V/UHF Subsystem Functions 2.15.1.1.Continuous frequency scanning, independent DF measurement and wideband acquisition mode to detect and simultaneously measure multiple signal parameters including DF for all detected emitters in an instantaneous bandwidth of ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). 2.15.1.2.Single frequency DF mode that permits manual tasking of the DF processor to provide continuous DF and monitoring on a single narrow band channel 2.15.1.3.Emitter 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 2.16. Detailed V/UHF Comms ES DF/MON Antenna Requirements 2.16.1.The salient features of the required V/UHF Communications ES DF and MON antenna shall be as follows: a.V/UHF DF antenna including multiple bands splits across the operating spectrum. b.DF Antenna mounted on pneumatic mast (30 feet) on the vehicle within 30 minutes or better. c.The DF and monitor antennas shall be ruggedized for the tactical environment and can withstand wind speeds found in the user country environment. d.Lightning protection. e.All antennas and their connectors shall be sealed and waterproofed that meet MIL-STD-810G. 2.17. Detailed V/UHF Comms ES Acquisition Subsystem Requirements 2.17.1.The salient features of the required V/UHF Communications ES acquisition subsystem shall be as follows: a.Frequency range, scan rate and instantaneous bandwidth of the acquisition sub-system shall be identical to V/UHF wideband DF subsystem b.Wideband signal acquisition subsystem synchronized with/directed by the DF processor able to intercept fixed frequency and frequency hopping signals 2.18. Detailed V/UHF Comms ES Signal Recognition Subsystem Requirements 2.18.1.The salient features of the required V/UHF Communications ES signal recognition subsystem shall be as follows: a.Recognition of analog modulation Types ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). b.Recognition of digital modulation types ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). c.Recognition of agile signal types ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). d.Number of Simultaneous Channels in Recognition is ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). 2.19. ES FAT 2.19.1.The FAT shall include a DF accuracy test and calibration to be conducted in a suitable testing range or anechoic chamber. 2.19.2.The FAT shall demonstrate that the system recognize and demodulate the all analog and digital signals described in 3.19 2.19.3.The FAT shall demonstrate all major functions including geolocation using 3 or more LOBs from different networked ES systems, detection of hoppers ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) and compliance with stated provisos 3.Electronic Attack (EA) 3.1.Introduction 3.1.1.The intent of the EA is to provide the capability to electronically attack (jam) communication radios operating in the VHF and UHF bands in a battlefield environment. An Electronic Warfare Operations Center (EWOC) shall be used as the Command and Control unit to task the EA of its EW Company. An Electronic Support (ES) sub-system shall be used to relay tasking/reports to/from the EA sub-system. The Communications EA units shall operate in a semi-automatic mode with minimal operator interaction, where the operator validates the semi-automatic decisions or in a manual mode by manually tuning the transmitters, choosing signals, accepting tasking and generating reports 3.2.Functional Requirements 3.2.1.The EA system shall provide the capability to electronically attack (jam) communication radios operating in the VHF and UHF bands in a battlefield environment. 3.2.2.The equipment shall be integrated into a military shelter (S280 with tunnel mounted generator) mounted on a Navistar unarmored 7000 4x4 series MV vehicle. If required, a trailer shall be used to carry an antenna. 3.2.3.All operation, control and configuration of equipment shall be performed locally and/or at the EWOC depending on the type of mission. 3.2.4.The EA units shall operate in a semi-automatic mode with minimal operator interaction, where the operator validates decisions or in a manual mode by manually tuning the transmitters, choosing signals, accepting tasking and generating reports. 3.2.5.Quantity (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 equipment 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. 3.2.6.Each EA shall be equipped with a Global Positioning System (GPS). 3.2.7.The EA subsystem should have four (4) Narrowband monitoring receivers and audio recording capabilities to support monitoring missions in the V/UHF frequency range to detect signals of interest. 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 ES sub-system. 3.3.Tasking 3.3.1.The tasking system shall support the scheduling of programmed tasks that integrates/combines different aspects and functions of the system into a single application. For example, schedule a jamming cycle. 3.3.2.The 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. 3.3.3.Task prioritization shall be supported. 3.4.EA Mission 3.4.1.Prioritized 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. 3.4.2.Jammer 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. 3.4.3.Start/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. 3.4.4.As 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. 3.5.EA Attack Capability 3.5.1.Look Through for a wideband (WB) system having an instantaneous bandwidth (IBW) of ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) (called a quote mark stare quote mark). This stare shall be moved anywhere on the RF spectrum from ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). 3.5.2.Detection - determines whether energy above a noise threshold is present in any frequency bin ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)), and if it is, generates an alarm to the controlling unit. 3.5.3.Look Up - Shall be implemented by transferring the target frequency information received by the ES or EWOC to the jamming scenario interface. 3.5.4.Lock Out Frequencies - Shall have the ability to accept at least 1,000 lockout frequencies. 3.5.5.Frequency Masks - Shall have a contiguous range of frequencies that are defined to be in use by friendly forces. 3.5.6.Barrage Range - Shall allow setting up frequency barrage ranges for jamming. 3.5.7.Shall deliver a J/S jamming signal of ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) over the entire frequency spectrum 30 - 3000 MHz at a stand-off distance of ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) km with the separation of the Red Force communication transceiver nodes being ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) km. 3.5.8.The Power Amplifier(s) shall be scalable depending on the target frequency. 3.5.9.The power of any amplifier shall be configurable by the operator. 3.5.10.The operator shall have the capability to determine the type of jamming signals he will employ from a set of available signals. The set shall include the same set of signals the ES is capable of recognizing. 3.5.11.The system shall have a zeroizing capability to completely erase any information in the database and any other residing nonvolatile information within ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)) minutes of initiation. 3.6.System Management & Configuration 3.6.1.The ability to set user and group policies and permissions to system resources shall be supported. 3.6.2.The ability to configure or manage any subsystem from a single configuration/ management module shall be supported. 3.6.3.Operator workstations shall have a fully updated Microsoft Windows operating system. 3.7.Monitoring 3.7.1.Shall have the ability to monitor database server status. 3.7.2.Shall have the ability to monitor all systems and subsystems to assure proper operation and performance. 3.7.3.Shall have a Built in Test (BIT). 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. 3.7.4.The troubleshooting sub-system shall be a comprehensive process that enables the operator to test all sub-systems with detailed results. 3.7.5.Whenever a sub-system fails, the monitoring mechanism shall trigger immediate alarms locally and at the EWOC. 3.7.6.The operator shall perform pre-mission check-outs to verify that the EA jamming equipment is operating properly. 3.8.EA Techniques Generator Features 3.8.1.The 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 EA mobile unit. EW jamming covering the tactical communications band of ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). 3.8.2.Shall have the ability to attack both conventional and frequency agile targets ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). 3.8.3.The EA shall effectively disrupt frequency hoppers by using advanced sweeping techniques. 3.8.4.The V/UHF Instantaneous bandwidth shall be ((Specific information to be provided to interested vendors via separate document. Please contact publisher.)). 3.8.5.Shall have the ability to attack 1 to 16 simultaneous targets in different frequency bands and be able to attack VHF/UHF bands concurrently not using a time division multiplexing method. 3.8.6.Shall have the ability to prioritize targets, so that the correct amount of power is delivered. 3.8.7.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. 3.8.8.The system shall be designed such that no more than two operators are needed to place the system into an operational configuration. The design shall factor in the need for expediency and the fact that the operators may be uniformed in tactical uniforms. 3.8.9.Tactical, 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. 3.8.10.The antennas are preferred to be bestowed on roof of shelter with a mechanism to secure it during transport. 3.9.EA FAT 3.9.1.Shall demonstrate that the system can generate the same signals that the ES can monitor and recognize and use them to jam the target of interest. 3.9.2.Shall demonstrate that the output power is the correct amount at the antenna output point. 4.Communications 4.1.Introduction 4.1.1.The communication equipment will be GFE. The capability will be provided by USG. 4.2.Intra-Site Communications 4.2.1.Intra-site communications shall be accomplished using 10/100/1000 MB Ethernet Local Area Network (LAN). 4.2.2.The computers and equipment within each shelter will communicate via TCP/IP sockets. 4.3.Inter-Site Communications 4.3.1.HCLOS Communications System 4.3.1.1.A HCLOS communications network shall be provided between the CO EWOC, ESs, and EAs. Harris 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 4.3.1.2.The features shall include: a.Voice and data communications. b.A telephone set or more shall be provided at each shelter for intra-site and inter-site VoIP connectivity. c.Management system to configure the radios and set up the communication links. d.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. e.Data rates that can accommodate tasking traffic, different functions, and any bandwidth consuming applications. f.Should support point-to-point (PTP) and point-to-multipoint (PTM) configurations. g.IP networking support. h.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 i.Mast mounted. If selected to be mounted on the EA shelter, should not affect the performance of the system. j.Support repeater configuration (radio relay) k.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. 4.3.2.HCLOS Radio Relay Towers 4.3.2.1.We estimate that for some regions in the user country, the distances between EW elements (ES, EA, and EWOC) will be more than 30 Km 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. 4.3.2.2.Each 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 1 depicts an example tower configuration. The configuration shall require 4 radios, i.e. 2 per tower. Figure 1. HCLOS Communications Network 4.3.3.Existing IP-Based Network Infrastructure 4.3.3.1.The EWOC shall have an IP interface to be directly connected to the existing IP network or through a router. 4.3.3.2.The 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. 4.3.3.3.The 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. US Army Communications- Electronics Command, CECOM Acquisition Center - DAAB07, ATTN: AMSEL-AC, Aberdeen Proving Ground, MD 21005
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/notices/30df0561e6260eda4efa50eefb60e5da)
 

Place of Performance

Address: ACC-APG - Aberdeen Division B HQ CECOM CONTRACTING CENTER, 6001 COMBAT DRIVE ABERDEEN PROVING GROU MD

Zip Code: 21005-1846
 

Record

SN03330324-W 20140406/140404234553-30df0561e6260eda4efa50eefb60e5da (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 |