2026.01.14 Q&A.pdf

• For the stated “detect and identify unknown UAS to at least 40 NMI (goal 100 NMI),” what target assumptions apply (UAS class/group, altitude/typical flight profiles, cooperative vs.

non-cooperative, desired identification level such as protocol/serial/operator geolocation)?

Required data at the stated distances are UAS location, altitude, vertical speed, horizontal speed, heading, operator position, serial number, with a historical flight path displayed and updated real-time.

• Which of the following are required versus objective (where legally/technically available):

type/model, serial number, UAS location, altitude/speed/heading, and operator location?

UAS location, altitude, vertical speed, horizontal speed, heading, operator position, serial number, with a historical flight path displayed and updated real-time.

• Are there specific interface standards, data formats, gateways, or CONOPS/SOP requirements the Government intends to mandate (or prefers) to support compatibility with FBI/USAF/USSF counter-UAS systems, procedures, and protocols? No NASA mandated protocols and systems and protocols can change over time, and it is expected that the offeror will have the insight and knowledge of existing protocols to ensure proper interface.

• Are there target thresholds for alert latency, track update rate, and acceptable false alarm rates (or an evaluation framework NASA intends to apply)? The requirement is for alerts to be annunciated as soon as the drone is detected with updates to be real-time with continuously updated data/tracks. There is no formal or specified false alarm rate, but false alarms are expected to me minimal or non-existent.

• The requirement calls for notifications and access independent of KSC communications infrastructure, including mobile device access over cellular. Should responders assume cellular connectivity is the primary path, or are alternate independent backhauls acceptable? Responders are at liberty to propose any system or data transmission method they choose as long as it is independent of NASA communications and IT systems.

• For planning purposes, do you anticipate Secret-cleared personnel on-site continuously, episodically (e.g., high-interest events), or primarily for coordination/analysis activities? Per the stated requirements, personnel will be required to be on-site for special/high-interest events, but there is no requirement for fulltime on-site presence. Personnel will also be expected to be on site as required for system setup, maintenance, upgrades, etc.

• Is NASA contemplating a formal site acceptance test and/or operational demonstration prior to start of performance (e.g., uptime threshold, detection demo, alerting demo), and if so, is there a draft outline? There will be an acceptance process to ensure the Government is receiving systems that operate as required.

• For the capability statement submission, does NASA expect respondents to include signed Letters of Intent / Letters of Commitment with any proposed HBCU/MSI teammates/subcontractors, or is a narrative description of the intended HBCU/MSI roles and partnering approach sufficient at this stage? There is no requirement for any Letters of Intent.

• We are seeking to compete as a Prime contractor, but we are also open to teaming and subcontracting where it improves mission readiness and reduces risk. While our leadership team has extensive aerospace and defense experience, our company is a newer small business with limited corporate past performance as a prime. For this requirement, does NASA anticipate that relevant experience from key personnel and major teammates/subcontractors will be considered to ensure capable newer entrants receive full and fair consideration? The Government has no requirements for specific skills or experience from offeror's staff.

• What role does the Kennedy Space Center (KSC) PMO foresee NSA/DISA-accredited hyperscale cloud services playing for the UAS work? The Government assumes no solutions for offeror's proposals.

• What role will NSA-accredited ‘Raise the Bar’ (RTB) compliant cross domain solutions (CDS) play in the UAS work? The Government assumes no solutions for offeror's proposals.

• Both the PWS and RFI list a detection and identification range of 40nm from the center of launch pad 39B. The requirement however does not specify the size of the UAS to be detected. Can NASA please verify this range and clarify this requirement by specifying the size of the UAS to be detected? The stated range is the requirement and there is no size limit, any UAS must be detected

• Are there restrictions on the use of Radars for this solution in terms of Band(s) used and power given the existing tracking and telemetry systems in use at the facility and the sensitivity of launch system and payload electronics? Yes, all radiating sources must be approved by the NASA-KSC Spectrum Manager for use on Kennedy Space Center. Restrictions are based on multiple variables including power levels, frequency, duration, and direction.

• The requirements in the RFI and PWS require the system to provide the type and serial number of the UAS. These details are generally only available from library-based RF detection systems that decode the telemetry and control signals between the operator and the UAS. Can NASA please clarify if the decoding for identification must be available at the 40nm range mentioned or is detection at the full range sufficient with identification only at a closer range? Yes, that data must be detectable at the specified ranges