Inactive

Request for Information (RFI) for Telemetry SNR Polling Sensor Development 1. Overview This document identifies the threshold technical requirements for a telemetry signal-to-noise-ratio (SNR) polling... Request for Information (RFI) for Telemetry SNR Polling Sensor Development 1. Overview This document identifies the threshold technical requirements for a telemetry signal-to-noise-ratio (SNR) polling sensor needed to support White Sands Missile Range's (WSMR) coupled sensor array development. This development will enable WSMR to better support challenging use case scenarios with more than five targets in the air such as complex ballistic intercepts, intricate aircraft scenarios, drone formations, and multiple precision guided bombs. Implementing the coupled sensor array solution will shift the mission support paradigm at WSMR from primarily using traditional single object tracking reflector antennas to also utilizing a fleet of coupled sensor arrays which will provide a large area of telemetry coverage. The current plan is for the Government to purchase COTS products such as triband feed horns, telemetry receivers, TMoIP boxes, etc. and integrate everything into a coupled sensor array solution. Since the SNR polling sensor is a new development the Government does not have the capability to build this technology in-house. This RFI is to conduct market research and to attain information on what is needed and the level of effort required for performing this SNR polling sensor development. 2. SNR Polling Sensor Operational Requirements The SNR polling sensor is the brains of the coupled sensor array solution responsible for processing all of the antenna RF inputs and selecting and routing the highest RF signal-to-noise-ratio (SNR) value from each of the designated mission frequencies (a minimum of 12 frequencies) to the appropriate telemetry receiver. The SNR polling sensor needs to support all of the 8 antenna inputs and have outputs to provide to each of the 12 telemetry receivers. 3. SNR Polling Sensor Technical Requirements: (All requirements are thresholds unless specifically marked an objective.) 3.1 The SNR polling sensor shall have 8 single channel RF inputs. When the SNR polling sensor is later integrated with the coupled sensor array solution these RF inputs will be provided by the triband feed horns. 3.2 The SNR polling sensor shall support L, S, and C-Band frequencies as defined in IRIG 106 (threshold). The SNR polling sensor shall support 1 -10 GHz (objective). All filtering will be performed by the RF input sources. 3.3 The SNR polling sensor shall support a minimum of 12 user definable frequencies. 3.4 The SNR polling sensor shall have a minimum of 12 RF outputs. 3.5 The SNR polling sensor shall have a remotely controllable graphical user interface (GUI). 3.6 The SNR polling sensor GUI shall be designed to minimize risks to system operations and cyber threats consistent with National Security Telecommunications and Information Systems Security Policy (NSTISSP) No. 11; DOD Instruction 8500.01, Cybersecurity; and AR 25-2 Section II 4-6, Security Implementation Specifications and Guides. 3.7 The SNR polling sensor shall meet the requirements to obtain an Authority-to-Operate (ATO) from the Authorizing Official (AO). 3.8 Each frequency selected by the SNR polling sensor shall be associated with a corresponding SNR polling sensor RF output. The relationship should be clearly displayed on the SNR polling sensor's GUI (e.g. frequency 1 to RF output 1). 3.9 There shall be an area reserved on the GUI for the operator to input user defined target descriptions near the frequency values. This will increase operator awareness especially as mission scenarios become more complex. 3.10 The SNR polling sensor solution shall have a maximum of a 3 dB loss measured from the RF inputs coming into the SNR polling sensor to the RF outputs leaving the SNR polling sensor. 3.11 The SNR polling sensor shall allow an operator to do a baseline RF zeroing of each RF input on the cold sky via the GUI. 3.12 The GUI shall display the signal strength of each frequency in absolute and relative power but not simultaneously. The choice of which to display will depend on whether or not the frequency's AGC signal level has been zeroed. 3.13 The SNR polling sensor shall perform a SNR based selection for each RF input at each frequency and output the highest element's SNR to the proper RF output. The SNR polling sensor will allow the RF input sources to be sent to zero or many RF outputs using a fan-out non-blocking switch architecture. At no point shall an RF output have two simultaneous RF inputs sources. The switching between RF inputs shall limit data dropouts. Here are a couple of examples: RF source 1 could have the highest SNR for all 12 frequencies and the SNR polling sensor would output the corresponding RF source 1 to each of the RF outputs. Conversely, RF source 1 could have 2 frequencies with the highest SNR, RF source 2 could have 2 frequencies with the highest SNR, RF source 3 could have 2 frequencies with the highest SNR, RF source 4 could have 2 frequencies with the highest SNR, and RF sources 5, 6, 7, and 8 could have 1 frequency with the highest SNR value. The various potential combinations are numerous. 3.14 The SNR polling sensor GUI shall have a selectable number of RF inputs to be used for the polling function (i.e. from 1 to 8). This will allow for the isolating of the RF sources to help with troubleshooting. 3.15 The SNR polling sensor shall support a 10 Hz scan rate for all RF inputs (threshold). The SNR polling sensor shall support a 100 Hz scan rate for all RF inputs (objective). A scan is defined by the system polling signal strength for all frequencies at all input sources. 3.16 The SNR polling sensor shall receive an IRIG B time input and have a visible display on the GUI highlighting the status of the station timing (e.g. green for good timing and red for an error). 3.17 The SNR polling sensor shall support a selectable hysteresis. The operator shall be able to select on the GUI the dB hysteresis value and the hysteresis time before switching elements to prevent rapid toggling between the different RF sources (e.g. if these items are set at a 3 dB hysteresis value and a 1 second time threshold it requires another element to be higher than 3 dB for 1 second before switching over to it). The specific RF output will switch once both the hysteresis values are met. 3.18 The SNR polling sensor GUI shall have a logging function where it records at 10 Hz (threshold) / 100 Hz (objective) the IRIG time, the AGC values for each RF input at every selected frequency, and a record of what RF input is sending RF to each output. 3.19 The GUI shall support a playback mode to play back log files. The GUI shall allow the operator to select which data to be played back. The GUI shall be clearly marked when the playback mode is in operation. 3.20 The SNR polling sensor's logging function shall be a simple button click on the main page of the GUI. 3.21 The SNR polling sensor shall be rack mountable and fit within 19 inches wide and 36 inches deep. 3.22 The SNR polling sensor shall operate using 208/120VAC 60 Hz power source. 3.23 The SNR polling sensor shall support redundant power supplies. 3.24 The SNR polling sensor shall have the necessary fans built in to provide sufficient cooling. 3.25 The SNR polling sensor shall have a self-test capability to report anomalies to the operator. Examples include a faulty time source, error writing to the log file, hardware issue related to one of the RF inputs or outputs, etc. 4. Sources Sought and RFI Submission The purpose of this RFI submission is to gain industry feedback on the level of effort needed to develop the SNR polling sensor technology. Industry feedback is vitally important and the Government will be receptive to all submissions. The Government is looking for companies who can provide or develop a timely solution. All respondents are asked to provide the following: 1. A technical description of your potential solution. The description should answer the following: a. Describe your solution and approach. b. How does the expected performance of your solution compare to the requirements stated above? c. How effectively have you developed similar solutions? d. What evidence exists that your proposed solution is applicable if it has not been used in similar systems? 2. A schedule estimate from contract award to operational capability. 3. Rough Order of Magnitude (ROM) price quote. How does the price quote change when considering a delivery of (5-8) units instead of just 1? Responses are requested by 12 September 2019. Joshua Dannhaus - email: joshua.r.dannhaus.civ@mail.mil Todd Kelley - email: todd.g.kelley.civ@mail.mil